Triple
T12902570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sri Srinivasan |
E308645
|
entity |
| Predicate | confirmationDateToDCCircuit |
P30904
|
FINISHED |
| Object | 2013-05-23 |
—
|
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: 2013-05-23 | Statement: [Sri Srinivasan, confirmationDateToDCCircuit, 2013-05-23]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confirmationDateToDCCircuit Context triple: [Sri Srinivasan, confirmationDateToDCCircuit, 2013-05-23]
-
A.
confirmedToCourtOn
Indicates that an entity has formally provided confirmation or testimony to a court regarding another entity or matter.
-
B.
sentenceConfirmationDate
Indicates the date on which a sentence (e.g., legal judgment or decision) is formally confirmed or finalized.
-
C.
confirmationVoteDate
chosen
Indicates the date on which a formal confirmation vote regarding an entity took place.
-
D.
mandateConfirmedDate
Indicates the date on which a mandate (such as an authorization or directive) was formally confirmed or validated.
-
E.
confirmedFor
Indicates that an entity has been officially approved, scheduled, or validated to participate in, receive, or be associated with another specified entity or event.
- 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971820e008190bf8bc7c392c8bcbb |
completed | April 10, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69d96fa776648190b9b5c30722ea50b6 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:40 p.m.