Triple
T4350525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Todos los Santos |
E98012
|
entity |
| Predicate | usedInVoyage |
P880
|
FINISHED |
| Object | Mendaña’s voyages to the Pacific |
—
|
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: Mendaña’s voyages to the Pacific | Statement: [Todos los Santos, usedInVoyage, Mendaña’s voyages to the Pacific]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInVoyage Context triple: [Todos los Santos, usedInVoyage, Mendaña’s voyages to the Pacific]
-
A.
shipUsed
chosen
Indicates that a particular ship was employed or utilized in carrying out an event, activity, or operation.
-
B.
usedWhenOnBoard
Indicates that something is employed or utilized while a person or object is on board a vehicle, vessel, or similar conveyance.
-
C.
usesAtSea
Indicates that something is employed, operated, or applied in a maritime or oceanic environment.
-
D.
aboardShip
Indicates that one entity is physically on or inside a ship, typically as a passenger, crew member, or cargo.
-
E.
usedInMaritimeNavigation
Indicates that something is employed as a tool, aid, or reference in the practice of maritime navigation.
- 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_69b3454965f881908c41190bb22f0e4b |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351a840248190b88c8a7be9158d25 |
completed | March 12, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69b34f51ed7c8190b7bf5f44b56b730d |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:15 p.m.