Triple
T21190106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arizona v. Johnson |
E522188
|
entity |
| Predicate | hasArguedDate |
P6917
|
FINISHED |
| Object | 2008-12-09 |
—
|
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: 2008-12-09 | Statement: [Arizona v. Johnson, hasArguedDate, 2008-12-09]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArguedDate Context triple: [Arizona v. Johnson, hasArguedDate, 2008-12-09]
-
A.
hasArguedYear
Indicates the year in which an argument, debate, or dispute involving the subject took place.
-
B.
arguedDate
chosen
Indicates the date on which an argument, debate, or legal case was formally presented or argued.
-
C.
hasDebatedStartDate
Indicates that there is an associated initial or tentative start date that has been discussed or debated rather than definitively set.
-
D.
hasAllegedDate
Indicates that an entity is associated with a date that is claimed or reported, but not confirmed as certain.
-
E.
hasDebatedStatus
Indicates that an entity has participated in or been assigned a particular status related to a debate or debating activity.
- 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e733372b488190920174955b4b9172 |
completed | April 21, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:07 p.m.