Triple
T3901893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States customary units |
E90512
|
entity |
| Predicate | dimensionSystem |
P52772
|
FINISHED |
| Object | length |
—
|
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: length | Statement: [United States customary units, dimensionSystem, length]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dimensionSystem Context triple: [United States customary units, dimensionSystem, length]
-
A.
dimensionType
Indicates the specific kind or category of dimension that characterizes how something is measured or structured.
-
B.
dimensionSymbol
Indicates a symbolic notation that represents or labels a specific dimension or measurement attribute in a context.
-
C.
dimension
Indicates that one entity specifies a measurable extent or size attribute (such as length, width, height, or similar quantitative property) of another entity.
-
D.
dimensionCharacteristic
Indicates that one entity specifies or describes a dimensional property or measurement characteristic of another entity.
-
E.
dimensionNote
Indicates that there is an explanatory note or annotation specifically about the dimensions or measurements associated with an entity or relationship.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69aef1aada308190821a3dfa6af170b3 |
completed | March 9, 2026, 4:13 p.m. |
Created at: March 9, 2026, 3:21 p.m.