Triple
T10451243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North American Vertical Datum of 1988 |
E246427
|
entity |
| Predicate | definesHeightsRelativeTo |
P18367
|
FINISHED |
| Object | mean sea level |
—
|
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: mean sea level | Statement: [North American Vertical Datum of 1988, definesHeightsRelativeTo, mean sea level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesHeightsRelativeTo Context triple: [North American Vertical Datum of 1988, definesHeightsRelativeTo, mean sea level]
-
A.
heightReference
chosen
Indicates that one entity’s height is being measured, compared, or defined relative to another specified reference point or standard.
-
B.
heightContext
Indicates a contextual or situational relationship that specifies how an entity’s height is defined, measured, or interpreted in a particular setting or frame of reference.
-
C.
hasHeight
Indicates that one entity possesses a specific vertical measurement or stature.
-
D.
typicalHeight
Indicates the usual or characteristic height associated with an entity, such as a person, object, or species.
-
E.
structureHeight
Indicates that a structure has a specific vertical measurement or height.
- 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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4fe0a6a548190a54212912f618e4e |
completed | April 7, 2026, 12:52 p.m. |
| PD | Predicate disambiguation | batch_69d4fb73a5e48190a8df4775bc5da80f |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:17 p.m.