Triple
T37502657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Septimus Roe |
E932006
|
entity |
| Predicate | honouredInPlaceName |
P116229
|
FINISHED |
| Object | Roe Highway |
—
|
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: Roe Highway | Statement: [John Septimus Roe, honouredInPlaceName, Roe Highway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honouredInPlaceName Context triple: [John Septimus Roe, honouredInPlaceName, Roe Highway]
-
A.
hasPlaceNamesakeIn
Indicates that something is named after a particular place or location.
-
B.
honoredOn
Indicates that an entity is formally recognized, celebrated, or commemorated on a specific date or occasion.
-
C.
honourOf
Indicates that one entity is the source, bearer, or cause of another entity’s honor, prestige, or distinguished recognition.
-
D.
namedInHonorBy
chosen
Indicates that one entity has been used as the namesake or dedicatee by another entity, signifying that the latter is named in honor of the former.
-
E.
commemoratedIn
Indicates that something is honored, remembered, or recognized within a particular work, event, place, or medium.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.