Triple
T1067881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victoria (ship) |
E23253
|
entity |
| Predicate | voyageObjective |
P15346
|
FINISHED |
| Object | reach the Spice Islands by sailing west |
—
|
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: reach the Spice Islands by sailing west | Statement: [Victoria (ship), voyageObjective, reach the Spice Islands by sailing west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voyageObjective Context triple: [Victoria (ship), voyageObjective, reach the Spice Islands by sailing west]
-
A.
purposeOfVoyages
chosen
Indicates the intended goals, reasons, or objectives motivating or justifying specific voyages.
-
B.
journeyDestination
Indicates that one entity serves as the endpoint or intended destination of another entity’s journey or travel.
-
C.
missionPlanning
Indicates the process of defining, organizing, and coordinating actions or operations needed to achieve a specific mission objective.
-
D.
scienceGoals
Indicates the objectives or intended outcomes that guide and justify a scientific activity, project, or investigation.
-
E.
mission
Indicates that an entity is assigned or engaged in a specific task, operation, or purpose-directed undertaking.
- 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_69a493ee1f908190992b5f0d1b04459b |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b9e1047481909af1cf8df2a01fff |
completed | March 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69a4b736f1e881909bace735b38c0ade |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.