Triple
T25408478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strait Crossing Bridge Limited |
E636622
|
entity |
| Predicate | primaryAssetOperated |
P71746
|
FINISHED |
| Object | Confederation Bridge |
—
|
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: Confederation Bridge | Statement: [Strait Crossing Bridge Limited, primaryAssetOperated, Confederation Bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryAssetOperated Context triple: [Strait Crossing Bridge Limited, primaryAssetOperated, Confederation Bridge]
-
A.
operatedAsset
chosen
Indicates that one entity is responsible for operating, managing, or running a particular asset.
-
B.
primaryAsset
Indicates that one entity is the main or most important asset associated with another entity.
-
C.
primaryOperation
Indicates the main or most important operation performed or used by an entity in a given context.
-
D.
operatedAs
Indicates that an entity functioned or was used in the capacity, role, or identity of another entity for some period of time.
-
E.
operatesPrimarilyOn
Indicates that one entity is mainly or chiefly used to act upon, affect, or process another entity.
- 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_69e75db361d881908d8701c856da6413 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: April 21, 2026, 1:52 p.m.