Triple
T15346369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fulgencio Yegros |
E366928
|
entity |
| Predicate | hasCitizenshipStartTime |
P31432
|
FINISHED |
| Object | at Paraguayan independence |
—
|
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: at Paraguayan independence | Statement: [Fulgencio Yegros, hasCitizenshipStartTime, at Paraguayan independence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCitizenshipStartTime Context triple: [Fulgencio Yegros, hasCitizenshipStartTime, at Paraguayan independence]
-
A.
citizenshipGrantedYear
Indicates the specific year in which an entity was officially granted citizenship.
-
B.
citizenshipDuringLifetime
chosen
Indicates that an entity held citizenship in a particular country or political unit at some point during its lifetime.
-
C.
dateOfCitizenshipChange
Indicates the date on which an entity’s citizenship status was changed from one nationality to another.
-
D.
citizenshipDuration
Indicates the length of time an entity has held citizenship in a particular country or jurisdiction.
-
E.
hasTypicalCitizenship
Indicates that an entity is generally or commonly a citizen of a specified country or jurisdiction.
- 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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e1749bc8190a8b9cbcb27288a5b |
completed | April 16, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_69deca991e5081908b0df3d1ee7d5338 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:17 a.m.