Triple
T4477510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Álvaro de Mendaña de Neira |
E100044
|
entity |
| Predicate | expeditionRole |
P24306
|
FINISHED |
| Object | leader of Spanish Pacific expeditions |
—
|
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: leader of Spanish Pacific expeditions | Statement: [Álvaro de Mendaña de Neira, expeditionRole, leader of Spanish Pacific expeditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expeditionRole Context triple: [Álvaro de Mendaña de Neira, expeditionRole, leader of Spanish Pacific expeditions]
-
A.
roleInExpedition
chosen
Indicates the specific function, duty, or position an entity holds within the context of a particular expedition.
-
B.
describesExpedition
Indicates that one entity provides a detailed account or characterization of an expedition undertaken by another entity.
-
C.
roleInMissions
Indicates the specific function, duty, or position an entity holds within one or more missions.
-
D.
expeditionObjective
Indicates the primary goal or purpose that an expedition is intended to achieve.
-
E.
typicalExpeditionMode
Indicates the usual or most common mode or method by which an expedition is conducted.
- 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_69b34553cbe48190afa8ac1cac285b86 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35728ed508190ba0e882fa62d8848 |
completed | March 13, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69b3563d63008190816e37027e761375 |
completed | March 13, 2026, 12:11 a.m. |
Created at: March 12, 2026, 11:35 p.m.