Triple
T18566262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IAS 12 |
E453766
|
entity |
| Predicate | includesGuidanceOn |
P18444
|
FINISHED |
| Object | uncertain tax positions |
—
|
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: uncertain tax positions | Statement: [IAS 12, includesGuidanceOn, uncertain tax positions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesGuidanceOn Context triple: [IAS 12, includesGuidanceOn, uncertain tax positions]
-
A.
providesGuidanceTo
chosen
Indicates that one entity offers direction, advice, or instruction to another entity.
-
B.
guidanceType
Indicates the specific kind or category of guidance being provided or referenced in the relationship between entities.
-
C.
hasGuideline
Indicates that one entity is governed, informed, or constrained by a rule, standard, or recommended procedure provided by another entity.
-
D.
usesGuidanceKit
Indicates that one entity employs or relies on a guidance kit to direct, control, or navigate another entity or process.
-
E.
guidanceIntegration
Indicates how one entity incorporates, applies, or aligns with the advice, instructions, or direction provided by another entity.
- 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_69e53afe3ee081909eeee62c889948f4 |
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.