Triple
T1405113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish złoty |
E31673
|
entity |
| Predicate | minorUnitToMajor |
P27636
|
FINISHED |
| Object | 100 |
—
|
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: 100 | Statement: [Polish złoty, minorUnitToMajor, 100]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minorUnitToMajor Context triple: [Polish złoty, minorUnitToMajor, 100]
-
A.
minorUnitName
Indicates the name assigned to a smaller or subordinate unit within a larger structured entity or system.
-
B.
minorUnitUsage
Indicates how a minor or subordinate unit is used or functions in relation to a larger or primary unit.
-
C.
isMajor
Indicates that an entity holds primary or greater significance, importance, or rank relative to others in a given context.
-
D.
majorVersion
Indicates that one entity specifies or corresponds to the primary (major) version number of another entity in a versioning scheme.
-
E.
historicalSubunitToUnit
Indicates that one entity was historically a subunit, subdivision, or component of another larger entity.
- 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_69a49918e1f88190ba610f9dc8114578 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3bc55a08190a4dfe13a5378aff3 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bf030a388190bc82d30b9233e873 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c11067b48190bca6ef3ac1475c20 |
completed | March 1, 2026, 10:43 p.m. |
Created at: March 1, 2026, 7:59 p.m.