Triple
T632429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 20022 |
E15950
|
entity |
| Predicate | firstEditionPublished |
P15299
|
FINISHED |
| Object | 2004 |
—
|
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: 2004 | Statement: [ISO 20022, firstEditionPublished, 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstEditionPublished Context triple: [ISO 20022, firstEditionPublished, 2004]
-
A.
firstEditionPrintRun
Indicates the initial quantity of copies produced when a work is printed in its first published edition.
-
B.
firstEditionResult
Indicates that one entity is the outcome, record, or result associated specifically with the first edition of another entity.
-
C.
firstPublisher
Indicates that an entity is the original or earliest publisher of another entity (such as a work, edition, or resource).
-
D.
firstEditionSoldOutTime
Indicates the point in time at which the first edition of an item became completely sold out.
-
E.
initialPublication
chosen
Indicates the relationship in which a work is first formally published or made publicly available.
- 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_69a4935c131c8190a5378c6bf101e8cc |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49ec2a4c08190bc5c6ce8a10b0967 |
completed | March 1, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69a49d030c648190ba1a02301b45f694 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.