Triple
T24119154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Francisco de Bobadilla |
E597602
|
entity |
| Predicate | replacedAsGovernorOfHispaniola |
P154923
|
FINISHED |
| Object | Christopher Columbus |
—
|
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: Christopher Columbus | Statement: [Francisco de Bobadilla, replacedAsGovernorOfHispaniola, Christopher Columbus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedAsGovernorOfHispaniola Context triple: [Francisco de Bobadilla, replacedAsGovernorOfHispaniola, Christopher Columbus]
-
A.
reignAsKingOfSicily
Indicates that a person holds or has held the position of king ruling over Sicily.
-
B.
successorAsKingOfSicily
Indicates that one person became the next king of Sicily after another person.
-
C.
precededByAsRegentOfSicily
Indicates that one entity previously served as regent of Sicily immediately before another entity in a succession of regents.
-
D.
reignAsKingOfSicilyEnd
Indicates the point in time or event at which an individual's reign as king of Sicily comes to an end.
-
E.
captaincyOf
Indicates that one entity holds the role or position of captain for another entity, such as a team, group, or vessel.
- 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_69e288c74200819098ab875b592cb39f |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dee1a2608190870ade02495c5ebe |
completed | April 29, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
| PDg | Predicate description generation | batch_69f17c28b684819084eea522126463f8 |
completed | April 29, 2026, 3:34 a.m. |
Created at: April 17, 2026, 11:05 p.m.