Triple
T5817123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Court of Auditors |
E129013
|
entity |
| Predicate | auditScope |
P11084
|
FINISHED |
| Object | EU budget |
—
|
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: EU budget | Statement: [European Court of Auditors, auditScope, EU budget]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: auditScope Context triple: [European Court of Auditors, auditScope, EU budget]
-
A.
oversightScope
chosen
Indicates the range or extent of responsibilities and activities that fall under an entity’s oversight or supervisory authority.
-
B.
accessScope
Indicates the extent or boundaries of access that one entity has to another entity or resource.
-
C.
coverageScope
Indicates the extent or range of entities, conditions, or situations that are included under a particular coverage or applicability.
-
D.
reviewScope
Indicates the extent, boundaries, or aspects of something that are covered, considered, or evaluated during a review.
-
E.
organizationalScope
Indicates the range or extent of responsibility, authority, or applicability that an action, policy, or relationship has within an organization or its sub-units.
- 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_69c0084869e881908d7859492183ca7b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0400f1af881908d376ea4793f6dea |
completed | March 22, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69c0333fdd7081908d829265caa2ac11 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:53 p.m.