Triple
T4575914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Financial Reporting Standards |
E123139
|
entity |
| Predicate | firstIssuedByIASB |
P15299
|
FINISHED |
| Object | 2001 |
—
|
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: 2001 | Statement: [International Financial Reporting Standards, firstIssuedByIASB, 2001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstIssuedByIASB Context triple: [International Financial Reporting Standards, firstIssuedByIASB, 2001]
-
A.
firstStandardApproved
Indicates that an entity is the earliest or initial standard that has received formal approval.
-
B.
firstMajorCodificationBy
Indicates that the object is the first major formal codification or systematic recording of the subject.
-
C.
firstDefinedBy
Indicates that one entity is the original source that formally introduced, specified, or defined another entity.
-
D.
issuerFoundedAs
Indicates that the issuer was originally established or created under a particular prior name, form, or organizational identity.
-
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_69bd46466c7081909d07f36be2d08804 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd58dfe3508190b21836079e951a3c |
completed | March 20, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69bd5228b70c8190ac48705e35a710c1 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:10 p.m.