Triple
T762425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mactan |
E16099
|
entity |
| Predicate | battleOpponent |
P18835
|
FINISHED |
| Object | Spanish expedition of Magellan |
—
|
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: Spanish expedition of Magellan | Statement: [Mactan, battleOpponent, Spanish expedition of Magellan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battleOpponent Context triple: [Mactan, battleOpponent, Spanish expedition of Magellan]
-
A.
decidingOpponent
Indicates that one entity is the opponent or counterpart responsible for making a decision that affects another entity.
-
B.
keyOpponents
Indicates that the subject has primary or most significant opponents identified by the object.
-
C.
opponentNationality
Indicates that the related entity is the country or nationality of the opponent in a competitive or adversarial context.
-
D.
opponentAtMidway
Indicates that one entity is the opposing side or competitor of another in the context of the Midway event, location, or stage.
-
E.
battledIn
Indicates that two or more entities engaged in a battle or conflict that took place at a specific location or during a particular event.
- 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_69a493684ee48190bd43b7c78da4aec8 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a6841f388190a6d08c3bf5c17fe4 |
completed | March 1, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69a4a5048a8081908d0542214142664a |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a58c0a84819094f07658dc651b36 |
completed | March 1, 2026, 8:46 p.m. |
Created at: March 1, 2026, 7:37 p.m.