Triple
T1405974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Algerian dinar |
E31691
|
entity |
| Predicate | symbolPlacement |
P2875
|
FINISHED |
| Object | after amount in common usage |
—
|
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: after amount in common usage | Statement: [Algerian dinar, symbolPlacement, after amount in common usage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolPlacement Context triple: [Algerian dinar, symbolPlacement, after amount in common usage]
-
A.
stylePositioning
Indicates how an entity is spatially or visually arranged or aligned relative to a reference frame or other elements.
-
B.
hasCurrencySignPlacement
chosen
Indicates where the currency sign is positioned relative to the numeric amount in a monetary value.
-
C.
positioning
Indicates the spatial or contextual arrangement of one entity relative to another or within a given environment.
-
D.
positionSpecific
Indicates that something applies only at, or is defined with respect to, a particular position or location within a larger structure or sequence.
-
E.
symbolType
Indicates the classification or category of a symbol based on its role, form, or function within a given system.
- 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_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. |
Created at: March 1, 2026, 7:59 p.m.