Triple
T32938286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Pinta |
E842591
|
entity |
| Predicate | firstLandfallDateApprox |
P69049
|
FINISHED |
| Object | 1492-10-12 |
—
|
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-10-12 | Statement: [La Pinta, firstLandfallDateApprox, 1492-10-12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstLandfallDateApprox Context triple: [La Pinta, firstLandfallDateApprox, 1492-10-12]
-
A.
dateOfLandfall
chosen
Indicates the specific calendar date on which a storm or similar event first makes landfall at a particular location.
-
B.
firstLandfallBy
Indicates the location or entity where something (typically a storm, traveler, or object) initially makes landfall or first arrives from a journey over water or air.
-
C.
firstLandfallYear
Indicates the calendar year in which something (typically a storm or similar event) first makes landfall.
-
D.
secondMajorLandfallDate
Indicates the calendar date on which an entity, such as a storm or similar event, makes its second significant landfall.
-
E.
firstCategory5LandfallDate
Indicates the date on which a storm first reached Category 5 intensity at landfall.
- 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_69f34949727c81909d195c97de3341c8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:20 a.m.