Triple
T366985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Half Eagle |
E7981
|
entity |
| Predicate | standardUnitRelation |
P11666
|
FINISHED |
| Object | half of an Eagle (10-dollar gold coin) |
—
|
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: half of an Eagle (10-dollar gold coin) | Statement: [Half Eagle, standardUnitRelation, half of an Eagle (10-dollar gold coin)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardUnitRelation Context triple: [Half Eagle, standardUnitRelation, half of an Eagle (10-dollar gold coin)]
-
A.
typeOfUnit
Indicates that one entity specifies the kind or category of measurement unit that the other entity belongs to.
-
B.
SIUnit
Indicates that something is expressed or measured using a unit from the International System of Units (SI).
-
C.
nativeUnit
Indicates that one unit is the original, inherent, or default measurement unit associated with a given quantity or entity.
-
D.
minorUnitUsage
Indicates how a minor or subordinate unit is used or functions in relation to a larger or primary unit.
-
E.
typicalUnitSize
Indicates the standard or most common size or quantity in which something is typically measured, packaged, or used.
- 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_69a2e7e880008190a6ad7e06e5d03007 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebe92c7c8190b49af2b2b461eacc |
completed | Feb. 28, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69a2e95ede588190998fdf3a6ea90498 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea0b23ec8190bef9d593162388a4 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.