Triple
T31920247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James E. McGreevey |
E814947
|
entity |
| Predicate | resignationEffectiveDate |
P6919
|
FINISHED |
| Object | 2004-11-15 |
—
|
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: 2004-11-15 | Statement: [James E. McGreevey, resignationEffectiveDate, 2004-11-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resignationEffectiveDate Context triple: [James E. McGreevey, resignationEffectiveDate, 2004-11-15]
-
A.
resignationDateOfRespondent
chosen
Indicates the date on which the respondent formally resigned from their position or role.
-
B.
leaveDate
Indicates the date on which an entity departs or ceases to be present at a given place or context.
-
C.
retirementDate
Indicates the date on which an entity stops its active role or service, typically marking the end of its professional or operational period.
-
D.
removedFromOfficeDate
Indicates the date on which an individual was officially removed or dismissed from holding a particular office or position.
-
E.
resignationDateOfCabinet
Indicates the date on which a particular cabinet formally resigned or ceased to hold office.
- 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_69f348f1df848190851bbfb988da3414 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b1f555fc8190936917339cafcd49 |
completed | May 3, 2026, 2:24 a.m. |
| PD | Predicate disambiguation | batch_69f6aca7081881909e96a8b05ec086bb |
completed | May 3, 2026, 2:02 a.m. |
Created at: May 1, 2026, 12:03 a.m.