Triple
T18348401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Foster v. Love |
E439601
|
entity |
| Predicate | concurrence |
P4521
|
FINISHED |
| Object | none |
—
|
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: none | Statement: [Foster v. Love, concurrence, none]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concurrence Context triple: [Foster v. Love, concurrence, none]
-
A.
concurrenceType
Indicates the specific manner or category in which two or more events, actions, or conditions occur together or overlap in time or effect.
-
B.
conciliationLedBy
Indicates that a conciliation process is directed, organized, or overseen by a specified leading party or entity.
-
C.
contention
Indicates a state of active disagreement, dispute, or conflict between entities over an issue, claim, or resource.
-
D.
concurringJustice
chosen
Indicates that a justice agrees with the court’s judgment or outcome but writes or joins a separate concurring opinion expressing different or additional reasoning.
-
E.
agreement
Indicates that two or more parties mutually consent to and accept shared terms, conditions, or understandings.
- 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_69d8b9175fec8190af865699b4e64d8c |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e514f66a4c8190a0ba53d3b349178a |
completed | April 19, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69e44fe91bc08190906518e1b120fcf0 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:37 a.m.