Triple
T10654501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Court of Audit |
E251053
|
entity |
| Predicate | sectorAudited |
P84204
|
FINISHED |
| Object | federal ministries |
—
|
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: federal ministries | Statement: [Federal Court of Audit, sectorAudited, federal ministries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sectorAudited Context triple: [Federal Court of Audit, sectorAudited, federal ministries]
-
A.
sectorInspected
chosen
Indicates that a particular sector or area has been examined or checked, typically for compliance, safety, or condition.
-
B.
sectorRecognized
Indicates that an entity has been formally acknowledged or classified within a particular sector or industry.
-
C.
typeOfAudit
Indicates the specific category or kind of audit being performed or referenced in relation to an entity.
-
D.
sectorManaged
Indicates that one entity is responsible for administering, overseeing, or directing the operations of a particular sector.
-
E.
isSectorSpecific
Indicates that something is tailored or restricted to a particular industry or sector rather than being generally applicable.
- 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_69d6aa5a4c4881908f39be6efe5981e5 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6dff94c188190b1a822c3720d18b7 |
completed | April 8, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69d6dd8753108190b799ffa0c760526e |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:06 p.m.