Triple
T37506158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas v. Pennsylvania |
E932096
|
entity |
| Predicate | proceduralOutcome |
P83617
|
FINISHED |
| Object | no merits hearing held |
—
|
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: no merits hearing held | Statement: [Texas v. Pennsylvania, proceduralOutcome, no merits hearing held]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proceduralOutcome Context triple: [Texas v. Pennsylvania, proceduralOutcome, no merits hearing held]
-
A.
proceduralStatus
chosen
Indicates the current stage, condition, or progress state of a procedure or process.
-
B.
administrativeOutcome
Indicates the result or consequence of an administrative process, decision, or action taken by an authority.
-
C.
initialOutcome
Indicates the result or state that first occurs at the beginning of a process, event, or interaction, before any subsequent changes or outcomes.
-
D.
temporaryOutcome
Indicates that a result or state produced by an action or process is provisional and expected to change or be replaced later.
-
E.
proposalOutcome
Indicates the result or status assigned to a proposal after it has been evaluated or decided upon.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.