Triple
T29947567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rue Léon-Foucault |
E760677
|
entity |
| Predicate | namedForCenturyOfEponym |
P132332
|
FINISHED |
| Object | 19th century |
—
|
LITERAL FINISHED |
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: 19th century | Statement: [Rue Léon-Foucault, namedForCenturyOfEponym, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedForCenturyOfEponym Context triple: [Rue Léon-Foucault, namedForCenturyOfEponym, 19th century]
-
A.
hasEponymCentury
chosen
Indicates that something is named after a person associated with a particular century.
-
B.
namedAfterCentury
Indicates that something is named after a specific century, typically reflecting that century’s time period or characteristics.
-
C.
associatedWithCenturyOfNameBearer
Indicates that an entity is linked to the historical century in which the person (name bearer) associated with it lived or is primarily known.
-
D.
notableFromCentury
Indicates that an entity is notably associated with, or best known from, a particular century.
-
E.
hasCenturyOfPersonCommemorated
Indicates the century in which the person being commemorated lived or was active.
- 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_69f2246562b881909d57622f4086d43d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 29, 2026, 6:24 p.m.