Triple
T668305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DEM |
E12914
|
entity |
| Predicate | usedInType |
P18110
|
FINISHED |
| Object | fiat money system |
—
|
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: fiat money system | Statement: [DEM, usedInType, fiat money system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInType Context triple: [DEM, usedInType, fiat money system]
-
A.
usedInInterface
Indicates that something is employed or incorporated as a component or element within a user interface.
-
B.
usedInCase
Indicates that something (such as an item, method, or piece of information) is employed or applied within a particular case or instance.
-
C.
usedInSignatureOf
Indicates that something (such as a type, parameter, or construct) appears as part of the formal signature of a function, method, or similar callable entity.
-
D.
isUsedAs
Indicates that one entity serves a particular function, role, or purpose as another entity.
-
E.
usedInOperation
Indicates that something (such as a tool, method, or resource) is employed or applied during the execution of a particular operation or procedure.
- 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_69a493355dec819098d4244b2fa34885 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49ff921288190a2e5edb201ba69ee |
completed | March 1, 2026, 8:22 p.m. |
| PD | Predicate disambiguation | batch_69a49d18942c819083b3d1887e505900 |
completed | March 1, 2026, 8:10 p.m. |
| PDg | Predicate description generation | batch_69a49fcf0cb4819096edea4037ca2c03 |
completed | March 1, 2026, 8:21 p.m. |
Created at: March 1, 2026, 7:36 p.m.