Triple
T10552198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brockville Railway Tunnel |
E248978
|
entity |
| Predicate | hasCrossSectionShape |
P73088
|
FINISHED |
| Object | arched |
—
|
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: arched | Statement: [Brockville Railway Tunnel, hasCrossSectionShape, arched]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCrossSectionShape Context triple: [Brockville Railway Tunnel, hasCrossSectionShape, arched]
-
A.
hasCrossSection
chosen
Indicates that one entity represents or possesses the cross-sectional shape, profile, or slice of another entity.
-
B.
crossesSectionOf
Indicates that one entity passes through or over a specific segment or portion of another entity.
-
C.
hasHoleShape
Indicates that an entity possesses a hole or opening characterized by a specific geometric or structural shape.
-
D.
hasCeilingShape
Indicates that an entity is characterized by or associated with a particular shape of its ceiling.
-
E.
hasBoundaryShape
Indicates that an entity is associated with, or characterized by, a specific geometric or spatial shape of its boundary.
- 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_69d381c733c08190ab1dd6239f5f34ae |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d52710869c81909b6db1a190825bad |
completed | April 7, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69d518fa0b4081909bffc936d78bd77b |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:34 p.m.