Triple
T18566416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IFRS Conceptual Framework for Financial Reporting |
E453769
|
entity |
| Predicate | recognitionConceptBasedOn |
P64521
|
FINISHED |
| Object | relevance |
—
|
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: relevance | Statement: [IFRS Conceptual Framework for Financial Reporting, recognitionConceptBasedOn, relevance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognitionConceptBasedOn Context triple: [IFRS Conceptual Framework for Financial Reporting, recognitionConceptBasedOn, relevance]
-
A.
usesConceptIdentifier
Indicates that one entity refers to or operates with a specific concept by means of its unique identifier.
-
B.
basingConcept
chosen
Indicates that one concept serves as the foundational basis or underlying rationale for another concept.
-
C.
hasConcept
Indicates that an entity includes, embodies, or is associated with a particular concept.
-
D.
categoryConcept
Indicates that one entity serves as a categorical type or conceptual class under which the other entity is grouped or classified.
-
E.
commonConcept
Indicates that two or more entities share the same underlying idea, notion, or conceptual meaning.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53aff027481909ca7257967967650 |
completed | April 19, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69e478c16e0c8190b03966aa23c395a6 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:43 a.m.