Triple
T8232557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miguel Primo de Rivera |
E192326
|
entity |
| Predicate | deFactoPosition |
P3707
|
FINISHED |
| Object | dictator of Spain |
—
|
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: dictator of Spain | Statement: [Miguel Primo de Rivera, deFactoPosition, dictator of Spain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deFactoPosition Context triple: [Miguel Primo de Rivera, deFactoPosition, dictator of Spain]
-
A.
deFactoStatus
Indicates that one entity holds a role, position, or status in practice or by custom, even if it is not formally or legally recognized.
-
B.
deFactoRole
chosen
Indicates that an entity effectively functions in a role or capacity in practice, even if that role is not formally or officially assigned.
-
C.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
D.
positionA
Indicates the spatial or ordered position of an entity A within a defined reference frame or sequence.
-
E.
draftPosition
Indicates the selection order or specific pick at which an entity (such as a player) was chosen in a draft process.
- 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_69ca82db5b90819085d1ad7c2e27bfcc |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb782658fc8190885dc267355ff245 |
completed | March 31, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69cb36b1dea0819091418072501e79c1 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:46 p.m.