Triple
T30743412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucayans |
E782751
|
entity |
| Predicate | firstEuropeanContactYear |
P10100
|
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: [Lucayans, firstEuropeanContactYear, 1492]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstEuropeanContactYear Context triple: [Lucayans, firstEuropeanContactYear, 1492]
-
A.
firstContactWithEuropeans
chosen
Indicates that this marks the initial recorded encounter or interaction between a group and European people.
-
B.
yearOfEuropeanExploration
Indicates the specific year in which a European exploration of the referenced entity took place.
-
C.
firstEuropeanLandingDate
Indicates the date on which Europeans first arrived at or made landfall in a particular place.
-
D.
dateOfFirstEuropeanLanding
Indicates the date on which Europeans first arrived at or made landfall on a particular place.
-
E.
firstVoyageYear
Indicates the calendar year in which an entity (such as a vessel or traveler) undertook its first voyage.
- 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_6a0324c2d618819093f7e6424b0f5baf |
completed | May 12, 2026, 1:01 p.m. |
| PD | Predicate disambiguation | batch_6a0324292e588190b37d0c3016ea2062 |
completed | May 12, 2026, 12:59 p.m. |
Created at: April 29, 2026, 8:38 p.m.