Triple
T9169124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JOD |
E220039
|
entity |
| Predicate | fractionalStructure |
P12374
|
FINISHED |
| Object | 1 Jordanian dinar = 100 piastres |
—
|
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: 1 Jordanian dinar = 100 piastres | Statement: [JOD, fractionalStructure, 1 Jordanian dinar = 100 piastres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fractionalStructure Context triple: [JOD, fractionalStructure, 1 Jordanian dinar = 100 piastres]
-
A.
segmentStructure
Indicates that one entity represents a structural or organizational subdivision (a segment) within the overall structure of another entity.
-
B.
finStructure
Indicates a relationship where one entity specifies or characterizes the fin-related structural features or configuration of another entity.
-
C.
hasFraction
chosen
Indicates that one entity represents a fractional part or proportion of another entity.
-
D.
branchStructure
Indicates how the parts of a branching system are organized and connected relative to one another.
-
E.
integratedStructure
Indicates that multiple components are combined into a single, cohesive structure that functions as an integrated whole.
- 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_69ca83e467108190abcae6a33b3d4dad |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccaae0f3148190b111b22902cdb86c |
completed | April 1, 2026, 5:19 a.m. |
| PD | Predicate disambiguation | batch_69cc660761d88190ab6134b43b376964 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:22 p.m.