Triple
T15037566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CAD |
E378515
|
entity |
| Predicate | formatStandard |
P8032
|
FINISHED |
| Object | ISO 4217 three-letter code |
—
|
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: ISO 4217 three-letter code | Statement: [CAD, formatStandard, ISO 4217 three-letter code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formatStandard Context triple: [CAD, formatStandard, ISO 4217 three-letter code]
-
A.
format
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
B.
formatAfter
Indicates that one entity’s format or structural arrangement is derived from, follows, or is applied subsequent to another entity’s format.
-
C.
formatMayChange
Indicates that the format or structure of something is subject to modification and may not remain consistent over time.
-
D.
formatBefore
Indicates that one item’s format or formatting must occur or be applied prior to another item’s format or formatting.
-
E.
standardizedFor
chosen
Indicates that something has been adjusted or converted to conform to a common standard, format, or reference so it can be consistently compared or used.
- 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_69d85cd46b2c819090d054c27787f677 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded82cf3848190b0b2b6c9e65bc70b |
completed | April 15, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69de9a69d7848190b2b4662dd30f20e9 |
completed | April 14, 2026, 7:50 p.m. |
Created at: April 10, 2026, 2:59 a.m.