Triple
T10378058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NAVD 88 |
E244556
|
entity |
| Predicate | referenceSurfaceType |
P1242
|
FINISHED |
| Object | orthometric height reference |
—
|
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 reference | Statement: [NAVD 88, referenceSurfaceType, orthometric height reference]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: referenceSurfaceType Context triple: [NAVD 88, referenceSurfaceType, orthometric height reference]
-
A.
surfaceType
chosen
Indicates the kind or classification of surface associated with an entity or interaction.
-
B.
referenceSurface
Indicates that one entity serves as the surface or base relative to which another entity is positioned, aligned, or defined.
-
C.
surfaceFeatureOf
Indicates that one entity is a surface-level characteristic, pattern, or feature belonging to or present on another entity.
-
D.
surfaceTypeAround
Indicates the type or nature of the surface that surrounds or is immediately adjacent to a given entity.
-
E.
notableSurface
Indicates that one entity is a surface or exterior of particular significance or prominence in relation to 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_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.