Triple
T8636328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Massey Tunnel |
E204530
|
entity |
| Predicate | hasPlannedReplacement |
P36091
|
FINISHED |
| Object | bridge project (proposed, revised over time) |
—
|
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: bridge project (proposed, revised over time) | Statement: [George Massey Tunnel, hasPlannedReplacement, bridge project (proposed, revised over time)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlannedReplacement Context triple: [George Massey Tunnel, hasPlannedReplacement, bridge project (proposed, revised over time)]
-
A.
plannedReplacement
chosen
Indicates that one entity is intended or scheduled to be replaced by another entity in the future.
-
B.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by another entity.
-
C.
hasReplaced
Indicates that one entity has taken the place or function of another entity, superseding it in a given context.
-
D.
mayBeReplacedBy
Indicates that one entity can potentially be substituted or superseded by another entity.
-
E.
isPlannedToBeReplacedAsCapitalBy
Indicates that one capital city is intended or scheduled to be superseded by another as the official capital.
- 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_69ca834b903c8190add96cc651e1a477 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc47944d1c819081f448f14d04bf9d |
completed | March 31, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69cc455d6d448190a2da2a319ac78c37 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:27 p.m.