Triple
T18677236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Level Bridge (Edmonton) |
E456631
|
entity |
| Predicate | hasHeightCharacteristic |
P90499
|
FINISHED |
| Object | high-level crossing above river |
—
|
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: high-level crossing above river | Statement: [High Level Bridge (Edmonton), hasHeightCharacteristic, high-level crossing above river]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeightCharacteristic Context triple: [High Level Bridge (Edmonton), hasHeightCharacteristic, high-level crossing above river]
-
A.
hasHeight
Indicates that one entity possesses a specific vertical measurement or stature.
-
B.
hasSignificantHeight
Indicates that one entity’s height is notably large or substantial relative to a given standard or to other entities.
-
C.
estimatedHeadHeightInMeters
Indicates the estimated vertical height of a person's head, measured in meters.
-
D.
heightDescription
chosen
Indicates how tall an entity is, typically expressed in descriptive or qualitative terms rather than a precise measurement.
-
E.
heightInCentimetres
Indicates the numerical value of an entity’s height measured in centimetres.
- 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_69d8d38f72b4819090a935175d9ca8af |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e556b66680819082a268f1bf857db5 |
completed | April 19, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69e478db7a248190a8c6584673773923 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:48 a.m.