Triple
T18040487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xavier, Duke of Parma |
E431636
|
entity |
| Predicate | roleInCarlism |
P88009
|
FINISHED |
| Object | Carlist leader |
—
|
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: Carlist leader | Statement: [Xavier, Duke of Parma, roleInCarlism, Carlist leader]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInCarlism Context triple: [Xavier, Duke of Parma, roleInCarlism, Carlist leader]
-
A.
roleInMexicanWarOfIndependence
Indicates the specific part or function an entity played in the events or efforts of the Mexican War of Independence.
-
B.
royalistForcesCharacteristic
Indicates that a characteristic, trait, or attribute is associated specifically with royalist forces.
-
C.
roleInSpanishCivilWar
Indicates the specific involvement or function an entity had in the context of the Spanish Civil War.
-
D.
roleInRevolt
chosen
Indicates the specific function, position, or level of participation an entity had within a particular revolt or uprising.
-
E.
roleInAraucoWar
Indicates the specific function, position, or involvement an entity had within the context of the Arauco War.
- 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_69d8b9050fb48190890155145deb0a66 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4bfece6448190b4ba96075715bcef |
completed | April 19, 2026, 11:43 a.m. |
| PD | Predicate disambiguation | batch_69e3f908da508190a088aa837ea5b7af |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:25 a.m.