Triple
T3901911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States customary units |
E90512
|
entity |
| Predicate | lengthBaseUnit |
P25188
|
FINISHED |
| Object | yard (defined as exactly 0.9144 metre) |
—
|
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: yard (defined as exactly 0.9144 metre) | Statement: [United States customary units, lengthBaseUnit, yard (defined as exactly 0.9144 metre)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lengthBaseUnit Context triple: [United States customary units, lengthBaseUnit, yard (defined as exactly 0.9144 metre)]
-
A.
length
Indicates a measurement relationship where a value specifies how long something is from one end to the other.
-
B.
typeOfUnit
Indicates that one entity specifies the kind or category of measurement unit that the other entity belongs to.
-
C.
basedUnit
chosen
Indicates that one unit is defined in terms of, or derived from, another more fundamental unit.
-
D.
baseLengthOriginal
Indicates the original or initial length value of a base element before any changes or transformations.
-
E.
basedUnitType
Indicates that one unit is defined or derived in terms of another underlying (base) unit type.
- 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_69aed95d315881908cbf1bf4a7215fbf |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1abe2dc81909c18aeae9b286898 |
completed | March 9, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69aee75b5b808190a348a31b1325d3d0 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:21 p.m.