Triple
T16524107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Comissão de Censura |
E401390
|
entity |
| Predicate | controlledDomain |
P53339
|
FINISHED |
| Object | press |
—
|
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: press | Statement: [Comissão de Censura, controlledDomain, press]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlledDomain Context triple: [Comissão de Censura, controlledDomain, press]
-
A.
controlDomain
chosen
Indicates that one entity has authority over, manages, or regulates the scope, behavior, or operations of another entity or system.
-
B.
regulatoryDomain
Indicates that one entity defines or governs the rules, policies, or constraints under which another entity must operate.
-
C.
involvedDomain
Indicates that an entity participates in or is associated with a particular domain, field, or area of activity.
-
D.
affectedDomain
Indicates the domain, field, or area that is impacted or influenced by a given action, event, or condition.
-
E.
hasDomainRestriction
Indicates that the relationship or property is limited to applying only to entities within a specified domain or class.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32ed2622c8190b6429a49ca92284a |
completed | April 18, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69e296995d388190b88ebe189dce890d |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.