Triple
T30743242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | third voyage of Christopher Columbus |
E782746
|
entity |
| Predicate | firstLandingInSouthAmerica |
P134600
|
FINISHED |
| Object | 1498 |
—
|
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: 1498 | Statement: [third voyage of Christopher Columbus, firstLandingInSouthAmerica, 1498]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstLandingInSouthAmerica Context triple: [third voyage of Christopher Columbus, firstLandingInSouthAmerica, 1498]
-
A.
dateOfFirstEuropeanLanding
Indicates the date on which Europeans first arrived at or made landfall on a particular place.
-
B.
firstEuropeanLandingDate
Indicates the date on which Europeans first arrived at or made landfall in a particular place.
-
C.
firstEuropeanLandingInAreaBy
chosen
Indicates that the subject location is the place where the specified European individual or group first made landfall in that area.
-
D.
firstLandingOnAuyánTepuiBy
Indicates that the referenced entity is the person or group who made the first recorded landing on Auyán Tepui.
-
E.
firstToLand
Indicates that the subject is the earliest or initial entity to arrive at or touch down on a particular place or surface.
- 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a03232efd8481908ee25447a29ee20b |
completed | May 12, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_6a032269dcb08190907c965c28145b77 |
completed | May 12, 2026, 12:51 p.m. |
Created at: April 29, 2026, 8:38 p.m.