Triple
T24453902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palisadoes Airport |
E616623
|
entity |
| Predicate | arrivalEventDate |
P32352
|
FINISHED |
| Object | 21 April 1966 |
—
|
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: 21 April 1966 | Statement: [Palisadoes Airport, arrivalEventDate, 21 April 1966]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arrivalEventDate Context triple: [Palisadoes Airport, arrivalEventDate, 21 April 1966]
-
A.
arrivalAt
Indicates the event or state of an entity reaching and being present at a specific destination or location.
-
B.
subsequentArrivalDate
Indicates that one entity’s arrival date occurs after the arrival date of another related entity.
-
C.
arrivalDatePlanned
chosen
Indicates the date on which an arrival is scheduled or expected to occur according to a plan.
-
D.
entryDate
Indicates the date on which an entity was first recorded, created, or entered into a system or context.
-
E.
appointedOn
Indicates the specific date or time at which an entity is formally assigned or designated to a role, position, or responsibility.
- 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_69e2d7ef9fe08190a0613908758b4e86 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f298c4f1d881909d9119fec74afe53 |
completed | April 29, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:18 a.m.