Triple
T328022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chiafalo v. Washington |
E6561
|
entity |
| Predicate | wasArguedIn |
P6917
|
FINISHED |
| Object | 2020 |
—
|
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: 2020 | Statement: [Chiafalo v. Washington, wasArguedIn, 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasArguedIn Context triple: [Chiafalo v. Washington, wasArguedIn, 2020]
-
A.
arguesThat
Indicates that one entity presents reasons or justification in support of a specific claim, position, or proposition held about another entity or topic.
-
B.
arguedDate
chosen
Indicates the date on which an argument, debate, or legal case was formally presented or argued.
-
C.
wasContestedIn
Indicates that an event, position, or decision was the subject of competition, dispute, or challenge within a particular context or proceeding.
-
D.
debatedAt
Indicates that a debate or formal discussion involving the subject took place at the specified location or event.
-
E.
contestedBy
Indicates that one party challenges, disputes, or opposes a claim, decision, or position held by another party.
- 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_69a2e7933d6c8190bb2592ad13286ef2 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea98fa2c8190a5b44f4a26543a17 |
completed | Feb. 28, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69a2e94aab1c8190b8654708c87eeb91 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.