Triple
T37890148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Granville Bridge |
E945109
|
entity |
| Predicate | precededByStructureOpened |
P196270
|
FINISHED |
| Object | 1909 |
—
|
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: 1909 | Statement: [Granville Bridge, precededByStructureOpened, 1909]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precededByStructureOpened Context triple: [Granville Bridge, precededByStructureOpened, 1909]
-
A.
precededByInPosition
Indicates that one entity occurs or appears immediately before another entity in a specific ordered position or sequence.
-
B.
precededBySegment
Indicates that one segment occurs immediately before another segment in a sequence or ordering.
-
C.
previousStructure
Indicates that one structure directly precedes another in a defined sequence or configuration.
-
D.
precededBySpecial
Indicates that one event or entity occurs immediately before another in a context marked as special or exceptional compared to normal ordering.
-
E.
precededByInGroup
Indicates that one entity comes before another in the ordered sequence within the same group or collection.
- F. None of above. chosen
Provenance (4 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_69f76ef02668819089e7940c4001af5e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe189fec148190aeef51b417ba15b0 |
completed | May 8, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69fe17285b0881908de7569d8dbd20bd |
completed | May 8, 2026, 5:02 p.m. |
| PDg | Predicate description generation | batch_69fe189f2ea48190b8c4718f1353970e |
completed | May 8, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4:19 p.m.