Triple
T2751028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SYP |
E60986
|
entity |
| Predicate | hasMinorUnitExponent |
P36104
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [SYP, hasMinorUnitExponent, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMinorUnitExponent Context triple: [SYP, hasMinorUnitExponent, 2]
-
A.
minorUnitExponent
chosen
Indicates the power-of-ten exponent that defines how a minor unit relates in scale to its corresponding major unit.
-
B.
minorUnitsPerUnit
Indicates the number of smaller sub-units that collectively make up one whole unit in a given measurement or currency system.
-
C.
minorUnitToMajor
Indicates a conversion relationship where a quantity expressed in a smaller (minor) unit is translated into its corresponding amount in a larger (major) unit.
-
D.
minorUnitUsage
Indicates how a minor or subordinate unit is used or functions in relation to a larger or primary unit.
-
E.
minorUnitSubdivisions
Indicates that one administrative or organizational unit is subdivided into smaller, subordinate units.
- 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_69ab4b79846081909096725374d65ce9 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb6b6f0c8190901ab032dfb21e37 |
completed | March 7, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69abd82d005c81908a1ac7a1313c6d88 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.