Triple
T28332711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Collège de Château-Thierry |
E717576
|
entity |
| Predicate | hasNotablePupilName |
P3529
|
FINISHED |
| Object | Jean de La Fontaine |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Jean de La Fontaine | Statement: [Collège de Château-Thierry, hasNotablePupilName, Jean de La Fontaine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotablePupilName Context triple: [Collège de Château-Thierry, hasNotablePupilName, Jean de La Fontaine]
-
A.
notablePupil
chosen
Indicates that one person is a distinguished or noteworthy student or protégé of another person.
-
B.
hasNotableSurname
Indicates that an entity bears a surname that is recognized as notable, distinguished, or of particular significance.
-
C.
hasNameGivenTo
Indicates that one entity is the name that has been assigned or given to another entity.
-
D.
isNotableNameOf
Indicates that a name is widely recognized or distinguished as a significant identifier for the referenced entity.
-
E.
hasNotabilityFor
Indicates that an entity is notable, recognized, or significant specifically in relation to a given subject, context, or domain.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69eff6e9a57c8190a69c2c74b5d72119 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69ff1f3f94fc819095955299f50ab4ce |
completed | May 9, 2026, 11:49 a.m. |
| PD | Predicate disambiguation | batch_69ff1ea47748819082f63d9b9d9c3e65 |
completed | May 9, 2026, 11:46 a.m. |
Created at: April 28, 2026, 12:33 a.m.