Triple
T10377921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSRS |
E244553
|
entity |
| Predicate | historicalDatum |
P93666
|
FINISHED |
| Object | NAVD 88 |
E244556
|
NE 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: NAVD 88 | Statement: [NSRS, historicalDatum, NAVD 88]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: NAVD 88 Context triple: [NSRS, historicalDatum, NAVD 88]
-
A.
NAVD 88
chosen
NAVD 88 is the current official vertical datum used across the United States to provide a consistent reference for measuring elevations.
-
B.
NASAD
NASAD is a U.S.-based accrediting organization that sets national standards for undergraduate and graduate programs in art and design.
-
C.
NAF
NAF is a Norwegian trade union representing general workers across various industries.
-
D.
NAF
NAF is the aerial warfare branch of Nigeria’s Armed Forces, responsible for air defense, air operations, and supporting ground and naval forces.
-
E.
NAVAF
NAVAF is the United States Navy component command responsible for naval operations and security cooperation across the African continent and surrounding waters.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d4fb99ef088190b64661b2f42c320e |
completed | April 7, 2026, 12:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d7957e52108190a8d262b30a7d2780 |
completed | April 9, 2026, 12:03 p.m. |
Created at: April 6, 2026, 12:03 p.m.