Triple
T28284889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nescio Bridge |
E713254
|
entity |
| Predicate | hasSignificantHeightOverWater |
P51570
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Nescio Bridge, hasSignificantHeightOverWater, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignificantHeightOverWater Context triple: [Nescio Bridge, hasSignificantHeightOverWater, yes]
-
A.
elevationAboveWater
chosen
Indicates the vertical distance by which one entity is positioned above the surface level of a body of water.
-
B.
hasElevationRelativeToSeaLevel
Indicates the elevation or height of an entity measured relative to mean sea level.
-
C.
emergedAboveSeaLevel
Indicates that something rose or became exposed above the surface of the sea from a previously submerged or lower position.
-
D.
isMajorDeepWaterAreaOf
Indicates that one area constitutes a primary or significant deep-water region of another area or entity.
-
E.
hasHighestPointAboveSeaLevel
Indicates that the highest point of one entity is located at a greater elevation above sea level than that of 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_69efb52371d88190a1381c4e58a3b731 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 27, 2026, 11:25 p.m.