Triple
T32187410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hinkley |
E822142
|
entity |
| Predicate | legalCaseDefendant |
P2238
|
FINISHED |
| Object | Pacific Gas and Electric Company |
—
|
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: Pacific Gas and Electric Company | Statement: [Hinkley, legalCaseDefendant, Pacific Gas and Electric Company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalCaseDefendant Context triple: [Hinkley, legalCaseDefendant, Pacific Gas and Electric Company]
-
A.
defendant
chosen
Indicates that an entity is the party accused or sued in a legal action or proceeding.
-
B.
coDefendant
Indicates that two or more parties are jointly named and involved as defendants in the same legal case or proceeding.
-
C.
defendantStatus
Indicates the legal condition or standing of a defendant within a judicial or law-enforcement process.
-
D.
legalCase
Indicates a relationship where a formal legal dispute or proceeding exists between parties, typically adjudicated by a court or similar authority.
-
E.
hasMainDefendant
Indicates that a legal case or proceeding identifies a specific individual or entity as its primary defendant.
- 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_69f3490819cc81909bae1f8ce99423c5 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fed48d8e148190a99c0aea29f8a3ee |
completed | May 9, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fed3c82a24819095e614e31ac0307f |
completed | May 9, 2026, 6:27 a.m. |
Created at: May 1, 2026, 12:35 a.m.