Triple
T9109598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sebastian Cabot |
E218561
|
entity |
| Predicate | goalOfVoyages |
P15346
|
FINISHED |
| Object | finding a westward route to Asia |
—
|
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: finding a westward route to Asia | Statement: [Sebastian Cabot, goalOfVoyages, finding a westward route to Asia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalOfVoyages Context triple: [Sebastian Cabot, goalOfVoyages, finding a westward route to Asia]
-
A.
purposeOfVoyages
chosen
Indicates the intended goals, reasons, or objectives motivating or justifying specific voyages.
-
B.
voyageOn
Indicates that an entity is traveling or being transported aboard a particular vessel or means of sea (or space) travel.
-
C.
sponsoredVoyagesOf
Indicates that one entity provided financial or logistical support for the voyages undertaken by another entity.
-
D.
missionTo
Indicates that one entity is assigned, directed, or sent to carry out a specific mission involving another entity or location.
-
E.
intendedMission
Indicates that one entity is the planned or designated mission, task, or objective associated with another entity.
- 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_69ca83db7448819090d0a5de842ef2ac |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca845d9b0819084230e7cdd92dee0 |
completed | April 1, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69cc65fe5be081909d4470d6317b14a6 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:16 p.m.