Triple
T8556925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Francis Grover Cleveland |
E202592
|
entity |
| Predicate | birthDuring |
P63731
|
FINISHED |
| Object | Grover Cleveland presidency |
—
|
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: Grover Cleveland presidency | Statement: [Francis Grover Cleveland, birthDuring, Grover Cleveland presidency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: birthDuring Context triple: [Francis Grover Cleveland, birthDuring, Grover Cleveland presidency]
-
A.
bornDuring
chosen
Indicates that an entity’s birth occurred within the temporal span of a specified event, period, or time interval.
-
B.
birthEvent
Indicates an event in which an entity comes into existence by being born, typically linking the newborn to contextual details such as time, place, and participants.
-
C.
bornAfter
Indicates that one entity’s birth occurred later in time than another entity’s birth.
-
D.
bodyPartFromWhichBorn
Indicates the specific body part of an entity from which another entity is born or emerges.
-
E.
birthStatus
Indicates the condition or circumstances of an entity’s birth, such as whether and how it was born.
- 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_69ca8326e6c881908ff720d6abaebdc5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe946d1408190adc7dfb7b2173f9d |
completed | March 31, 2026, 3:33 p.m. |
| PD | Predicate disambiguation | batch_69cbd1160fcc8190aa380a73610af731 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:20 p.m.