Triple
T386984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Johns Bridge |
E8799
|
entity |
| Predicate | hasDeckHeight |
P5396
|
FINISHED |
| Object | approximately 205 feet above water |
—
|
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: approximately 205 feet above water | Statement: [St. Johns Bridge, hasDeckHeight, approximately 205 feet above water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDeckHeight Context triple: [St. Johns Bridge, hasDeckHeight, approximately 205 feet above water]
-
A.
hasHeight
Indicates that one entity possesses a specific vertical measurement or stature.
-
B.
hasDeckType
Indicates that an entity possesses or is associated with a specific type or category of deck.
-
C.
typicalHeight
Indicates the usual or characteristic height associated with an entity, such as a person, object, or species.
-
D.
observationDeckHeight
chosen
Indicates the vertical distance of an observation deck above a reference level, typically the ground or sea level.
-
E.
totalHeight
Indicates the combined vertical measurement resulting from adding the heights of one or more entities.
- 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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec5828d881909e8810061c02480c |
completed | Feb. 28, 2026, 1:23 p.m. |
| PD | Predicate disambiguation | batch_69a2e967d84c8190a6b647f78d95d4e4 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.