Triple
T34842438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Connecticut Appellate Reports |
E1004377
|
entity |
| Predicate | publishesOpinionsOf |
P101477
|
FINISHED |
| Object | Connecticut Appellate Court |
—
|
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: Connecticut Appellate Court | Statement: [Connecticut Appellate Reports, publishesOpinionsOf, Connecticut Appellate Court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publishesOpinionsOf Context triple: [Connecticut Appellate Reports, publishesOpinionsOf, Connecticut Appellate Court]
-
A.
publishedOpinionsAre
Indicates that certain opinions have been made publicly available or formally released in a published form.
-
B.
givesOpinionOn
Indicates that one entity expresses a view, judgment, or evaluation about another entity or subject.
-
C.
compiledOpinionsOf
chosen
Indicates that one entity has gathered, organized, or synthesized the opinions of another entity or group into a collective form.
-
D.
opinionBy
Indicates that a particular opinion, viewpoint, or judgment is expressed or held by a specific entity.
-
E.
unpublishedOpinionsAre
Indicates that certain opinions or judgments have not been formally published or made publicly available.
- 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_69f76db97714819099b5bed36fd64e9d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff6074bcd4819090b72cd6209ff206 |
completed | May 9, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69ff600aba888190812a6e7eca0283b8 |
completed | May 9, 2026, 4:25 p.m. |
Created at: May 3, 2026, 4 p.m.