Triple
T34489735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alfonso I of Aragon |
E885431
|
entity |
| Predicate | titleAfterConquest |
P40003
|
FINISHED |
| Object | King of Zaragoza |
—
|
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: King of Zaragoza | Statement: [Alfonso I of Aragon, titleAfterConquest, King of Zaragoza]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleAfterConquest Context triple: [Alfonso I of Aragon, titleAfterConquest, King of Zaragoza]
-
A.
afterConquestName
chosen
Indicates that an entity’s name is the one it is known by after a conquest or successful takeover has occurred.
-
B.
titleAfterSurrender
Indicates that one entity holds a title or designation that was granted or recognized only after a surrender, capitulation, or yielding event involving another entity.
-
C.
titleAfterExile
Indicates that an entity holds or receives a particular title only after a period of exile has occurred.
-
D.
titleAfterAnnexation
Indicates that an entity holds or is assigned a particular title specifically in the period following an annexation event.
-
E.
afterConquest
Indicates that one event, state, or condition occurs subsequent to and as a result of a conquest having taken place.
- 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_69f349cafcec8190997b45b3fdc16c27 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff3fb2318c81908a46c2f513608935 |
completed | May 9, 2026, 2:07 p.m. |
| PD | Predicate disambiguation | batch_69ff3e96dcc48190819f6204680d84aa |
completed | May 9, 2026, 2:03 p.m. |
Created at: May 1, 2026, 2:01 a.m.