Triple
T23735763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regan v. Wald |
E586536
|
entity |
| Predicate | hasDecidedDate |
P153466
|
FINISHED |
| Object | June 28, 1984 |
—
|
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: June 28, 1984 | Statement: [Regan v. Wald, hasDecidedDate, June 28, 1984]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDecidedDate Context triple: [Regan v. Wald, hasDecidedDate, June 28, 1984]
-
A.
hasFinalDecisionOn
Indicates that one entity holds the ultimate authority or responsibility to make and enforce a conclusive decision regarding another entity or matter.
-
B.
hasDecisionPoint
Indicates that there is a specific moment or juncture at which a choice between alternative options or paths must be made.
-
C.
hasPromDate
Indicates that one entity is the person who is accompanying another entity as their date to a prom event.
-
D.
hasDecisionForm
Indicates that an entity is associated with, or represented by, a particular decision document or formal decision record.
-
E.
decidedWith
Indicates that an entity made a decision jointly or in agreement with another entity.
- F. None of above. chosen
Provenance (4 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_69e24907dc9c8190be074c9c96a0ec2d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bad07bd08190b04d7a4c8732a856 |
completed | April 29, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f15adb23d88190ac2632299c26a9b3 |
completed | April 29, 2026, 1:11 a.m. |
Created at: April 17, 2026, 7:10 p.m.