Triple
T4089821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California v. Texas |
E87676
|
entity |
| Predicate | plaintiffsIncluded |
P1393
|
FINISHED |
| Object | individual plaintiffs in Texas |
—
|
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: individual plaintiffs in Texas | Statement: [California v. Texas, plaintiffsIncluded, individual plaintiffs in Texas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plaintiffsIncluded Context triple: [California v. Texas, plaintiffsIncluded, individual plaintiffs in Texas]
-
A.
claimantsInclude
Indicates that the specified set or group of claimants contains, as members, the entities referenced.
-
B.
partyTypePlaintiffs
Indicates the classification or category of the parties serving as plaintiffs in a legal action.
-
C.
includedWith
Indicates that one entity is provided or packaged together as part of another entity.
-
D.
includes
chosen
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
E.
formerlyIncluded
Indicates that an entity was previously part of, contained in, or a member of another entity, but is no longer included.
- 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_69aed94425148190be337845d56fac22 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefcab0a1c8190a1b0ca48ebc95b31 |
completed | March 9, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69aef909c9c88190b09d48dad325a83c |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:39 p.m.