Triple
T9158263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guanahani |
E219758
|
entity |
| Predicate | yearOfFirstEuropeanLanding |
P413
|
FINISHED |
| Object | 1492 |
—
|
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 | Statement: [Guanahani, yearOfFirstEuropeanLanding, 1492]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfFirstEuropeanLanding Context triple: [Guanahani, yearOfFirstEuropeanLanding, 1492]
-
A.
yearOfEuropeanExploration
chosen
Indicates the specific year in which a European exploration of the referenced entity took place.
-
B.
yearOfArrivalInNewWorld
Indicates the specific year in which an entity arrived in the New World.
-
C.
firstEuropeanClaimBy
Indicates that a place or territory was first formally claimed or asserted as possession by a specified European individual, group, or state.
-
D.
wasFirstPermanentEuropeanSettlementInAmericasFor
Indicates that one entity served as the first permanent European settlement in the Americas for another specified entity (such as a country, region, or group).
-
E.
firstVoyageEndYear
Indicates the calendar year in which an entity’s first voyage or initial journey was completed or came to an end.
- 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_69ca83e25418819093c6503deeaf30de |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca9d6b9ac819094efe12c1ed67ecf |
completed | April 1, 2026, 5:15 a.m. |
| PD | Predicate disambiguation | batch_69cc6605c6808190a30d92da006206ac |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:21 p.m.