Triple
T28479372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Military Directory of Spain |
E720648
|
entity |
| Predicate | apexLeader |
P164573
|
FINISHED |
| Object | Miguel Primo de Rivera |
—
|
NE NERFINISHED |
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: Miguel Primo de Rivera | Statement: [Military Directory of Spain, apexLeader, Miguel Primo de Rivera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: apexLeader Context triple: [Military Directory of Spain, apexLeader, Miguel Primo de Rivera]
-
A.
apexOf
Indicates that one entity is the highest or most extreme point, level, or culmination of another entity or process.
-
B.
apexTime
Indicates that an event or state occurs at the highest or peak point in time of another event or process.
-
C.
leagueLeader
Indicates that the subject entity is currently ranked first or holds the top position within a specified league or competitive grouping.
-
D.
pointsLeader
Indicates that the subject entity is the current leader in points relative to other entities in a given context or competition.
-
E.
leagueLeaderIn
Indicates that an entity is the current top-ranked or leading participant within a specified league or competition.
- 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_69f01a5983f48190b7c1b8857245a4f7 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f64ee7eb088190a195cefc30aa4fff |
completed | May 2, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64db8ee1881909362701d72ffe282 |
completed | May 2, 2026, 7:17 p.m. |
Created at: April 28, 2026, 2:54 a.m.