Triple
T9170169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CCPR |
E220060
|
entity |
| Predicate | typeOfDecisionsOnIndividualCommunications |
P2165
|
FINISHED |
| Object | Views (quasi-judicial decisions) |
—
|
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: Views (quasi-judicial decisions) | Statement: [CCPR, typeOfDecisionsOnIndividualCommunications, Views (quasi-judicial decisions)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfDecisionsOnIndividualCommunications Context triple: [CCPR, typeOfDecisionsOnIndividualCommunications, Views (quasi-judicial decisions)]
-
A.
decisionsAre
Indicates that certain choices, judgments, or resolutions possess a specified quality, status, or classification.
-
B.
includesDecisionsBy
Indicates that something contains, encompasses, or takes into account decisions made by a specified party or set of parties.
-
C.
decisionsTakenBy
Indicates that one or more decisions are made or taken by a specified agent or entity.
-
D.
decisionType
chosen
Indicates the specific category or nature of a decision associated with an entity or event.
-
E.
decisionsCalled
Indicates that one entity has made or issued formal decisions that are referred to or invoked 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_69ca83e467108190abcae6a33b3d4dad |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccaae23f048190847f12317be925b1 |
completed | April 1, 2026, 5:19 a.m. |
| PD | Predicate disambiguation | batch_69cc660761d88190ab6134b43b376964 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:22 p.m.