Triple
T9169153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JOD |
E220039
|
entity |
| Predicate | ISOStandardCategory |
P43031
|
FINISHED |
| Object | currencies |
—
|
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: currencies | Statement: [JOD, ISOStandardCategory, currencies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ISOStandardCategory Context triple: [JOD, ISOStandardCategory, currencies]
-
A.
isoClassificationStatus
Indicates the current status or stage of an entity within an ISO-based classification or standardization process.
-
B.
isStandardOf
Indicates that something serves as the recognized norm, reference, or benchmark by which another thing is defined, measured, or evaluated.
-
C.
standardsType
chosen
Indicates the classification or category of standards that apply to or are associated with an entity or activity.
-
D.
industryStandardFor
Indicates that something is widely accepted or recognized as the conventional or benchmark practice, specification, or norm within a particular industry.
-
E.
isStandard
Indicates that something conforms to an established norm, specification, or commonly accepted rule.
- 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.