Triple
T16153183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christopher Columbus |
E391964
|
entity |
| Predicate | ledVoyage |
P1561
|
FINISHED |
| Object | 1492 voyage to the Americas |
—
|
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: 1492 voyage to the Americas | Statement: [Christopher Columbus, ledVoyage, 1492 voyage to the Americas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ledVoyage Context triple: [Christopher Columbus, ledVoyage, 1492 voyage to the Americas]
-
A.
voyageOn
Indicates that an entity is traveling or being transported aboard a particular vessel or means of sea (or space) travel.
-
B.
voyageWith
Indicates that two or more entities travel together on the same journey or trip, sharing a common route or voyage.
-
C.
ledExpedition
chosen
Indicates that one entity organized and directed an expedition involving another entity or group.
-
D.
inspiredVoyage
Indicates that one entity’s ideas, actions, or example motivated another entity to undertake a particular journey or expedition.
-
E.
sponsoredVoyagesOf
Indicates that one entity provided financial or logistical support for the voyages undertaken by 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_69d87f1c65e48190aa2b4c472e9bafc4 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21d98d08c8190a15d4aee40d47220 |
completed | April 17, 2026, 11:46 a.m. |
| PD | Predicate disambiguation | batch_69e1828abb608190a99d86bce1d77de2 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:01 a.m.