Triple
T617499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Spanish Republic |
E14437
|
entity |
| Predicate | exiledGovernmentExistence |
P16685
|
FINISHED |
| Object | 1939-1977 |
—
|
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: 1939-1977 | Statement: [Second Spanish Republic, exiledGovernmentExistence, 1939-1977]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exiledGovernmentExistence Context triple: [Second Spanish Republic, exiledGovernmentExistence, 1939-1977]
-
A.
traditionallyExiledTo
Indicates that an entity has, by long-standing custom or tradition, been sent away or banished to a particular place.
-
B.
endedPoliticalEntity
Indicates that one political entity brought about the termination or dissolution of another political entity.
-
C.
formerPoliticalEntity
Indicates that an entity was once a political entity (such as a state, country, or polity) but no longer exists in that political form.
-
D.
causeOfExile
Indicates the reason or circumstance that led to an entity’s exile.
-
E.
sovereigntyStatus
Indicates the degree and type of political independence or control an entity holds over its own territory and governance.
- 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_69a4934b17c881909ace8270e8ddd202 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e2418c881908552d2c4a5006e97 |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49cfd15288190b4abdbd0bce3edcd |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49d76062c819083ac33f1f87097c7 |
completed | March 1, 2026, 8:11 p.m. |
Created at: March 1, 2026, 7:35 p.m.