Triple
T20219895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bruce Tunnel |
E495222
|
entity |
| Predicate | hasCrossSectionType |
P73088
|
FINISHED |
| Object | brick-lined horseshoe profile |
—
|
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: brick-lined horseshoe profile | Statement: [Bruce Tunnel, hasCrossSectionType, brick-lined horseshoe profile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCrossSectionType Context triple: [Bruce Tunnel, hasCrossSectionType, brick-lined horseshoe profile]
-
A.
hasCrossSection
chosen
Indicates that one entity represents or possesses the cross-sectional shape, profile, or slice of another entity.
-
B.
hasTypeOfCross
Indicates that an entity possesses or is associated with a specific type or style of cross.
-
C.
crossesSectionOf
Indicates that one entity passes through or over a specific segment or portion of another entity.
-
D.
hasSectionShape
Indicates that one entity possesses or is characterized by a particular cross-sectional shape specified by another entity.
-
E.
crossSectionDependsOn
Indicates that the value or behavior of a cross section is determined or influenced by another quantity, condition, or parameter.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66edc88148190b003b72eb4c69da5 |
completed | April 20, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69e55b18609481909ab28bc8750a642f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:39 p.m.