Triple
T11055012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coyle v. Smith |
E261350
|
entity |
| Predicate | decisionStatus |
P2165
|
FINISHED |
| Object | good law |
—
|
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: good law | Statement: [Coyle v. Smith, decisionStatus, good law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisionStatus Context triple: [Coyle v. Smith, decisionStatus, good law]
-
A.
statusDetermines
Indicates that the status or condition of one entity determines or governs the state, outcome, or behavior of another entity.
-
B.
decisionType
chosen
Indicates the specific category or nature of a decision associated with an entity or event.
-
C.
approvalStatus
Indicates the current state of authorization or acceptance granted to an entity or action.
-
D.
hasFinalDecisionOn
Indicates that one entity holds the ultimate authority or responsibility to make and enforce a conclusive decision regarding another entity or matter.
-
E.
decisionOutput
Indicates that a decision-making process produces or yields a particular outcome or result.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d798a0890481909c1d4f9d5b23f33a |
completed | April 9, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69d7440da46c8190a77380d5d747ac9c |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.