Triple
T28551362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austrian press |
E722892
|
entity |
| Predicate | selfRegulationBody |
P123431
|
FINISHED |
| Object | Austrian Press Council |
—
|
NE NERFINISHED |
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: Austrian Press Council | Statement: [Austrian press, selfRegulationBody, Austrian Press Council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selfRegulationBody Context triple: [Austrian press, selfRegulationBody, Austrian Press Council]
-
A.
isSelfRegulatory
Indicates that an entity has the capacity to monitor, control, and adjust its own behavior or internal processes without external direction.
-
B.
hasRegulatoryOrCulturalBody
Indicates that an entity is overseen, guided, or influenced by a formal regulatory authority or a culturally significant governing body.
-
C.
typeOfComplianceBody
chosen
Indicates that one entity is a compliance-related body or authority of the type specified by the other entity.
-
D.
sanctioningOrganization
Indicates the organization that formally imposes, authorizes, or enforces a sanction on another party.
-
E.
hasDisciplinaryBody
Indicates that an entity is overseen, regulated, or governed by a specific disciplinary or regulatory body.
- 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_69f01a60204481909af1bb76247b8221 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6504c5e1c8190903e5c4aeac37a30 |
completed | May 2, 2026, 7:28 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 3:42 a.m.