Triple
T10378059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NAVD 88 |
E244556
|
entity |
| Predicate | heightType |
P18367
|
FINISHED |
| Object | orthometric height |
—
|
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: orthometric height | Statement: [NAVD 88, heightType, orthometric height]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heightType Context triple: [NAVD 88, heightType, orthometric height]
-
A.
heightDescription
Indicates how tall an entity is, typically expressed in descriptive or qualitative terms rather than a precise measurement.
-
B.
heightFeet
Indicates a relationship where a subject has its vertical size or stature specified in feet as a unit of measurement.
-
C.
heightClass
Indicates the categorical height level or range to which an entity is assigned (e.g., short, medium, tall).
-
D.
heightReference
chosen
Indicates that one entity’s height is being measured, compared, or defined relative to another specified reference point or standard.
-
E.
heightInMetres
Indicates the height of an entity expressed as a measurement in metres.
- 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_69d381b3e328819094b23b8edcd29b5a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e98f312481909f7276fc3762d7bc |
completed | April 7, 2026, 11:25 a.m. |
| PD | Predicate disambiguation | batch_69d4dface5508190a7b42f01ad0a19a2 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 12:03 p.m.