Triple
T34524752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Distance Measuring Equipment |
E886369
|
entity |
| Predicate | displayUnit |
P8899
|
FINISHED |
| Object | nautical miles |
—
|
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: nautical miles | Statement: [Distance Measuring Equipment, displayUnit, nautical miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: displayUnit Context triple: [Distance Measuring Equipment, displayUnit, nautical miles]
-
A.
designationUnit
Indicates that one entity serves as the unit or standard of measure used to designate, label, or quantify another entity.
-
B.
inputUnit
Indicates that one entity serves as the unit of measurement or reference in which another entity’s value, quantity, or input is expressed.
-
C.
notationUnit
Indicates a relationship where one entity serves as a unit, symbol, or element within a system of notation used to represent information or structure.
-
D.
nativeUnit
chosen
Indicates that one unit is the original, inherent, or default measurement unit associated with a given quantity or entity.
-
E.
symbolUnit
Indicates that a symbol is associated with, or expressed in, a particular unit of measurement.
- 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_69f349cd7c148190aa99192b126d1527 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f727bde8f88190ad746ca515134ca1 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72739c30c81908642eef3feb3afcf |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 2:02 a.m.