Triple
T408764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Pole |
E9439
|
entity |
| Predicate | hasFirstAircraftOverflightDate |
P2088
|
FINISHED |
| Object | 1926 |
—
|
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: 1926 | Statement: [North Pole, hasFirstAircraftOverflightDate, 1926]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFirstAircraftOverflightDate Context triple: [North Pole, hasFirstAircraftOverflightDate, 1926]
-
A.
hasFormerAirport
Indicates that an entity previously had an airport that is no longer in operation or no longer exists.
-
B.
appliesToAirspaceOf
Indicates that a rule, restriction, or condition is specifically relevant to, or in effect within, a particular airspace.
-
C.
firstFlight
chosen
Indicates that the associated event or record corresponds to the earliest or initial flight taken or performed by the referenced entity.
-
D.
lastFlight
Indicates that one flight is the final or most recent flight taken or operated by a given entity within a specified context or sequence.
-
E.
hasCustomsAndImmigration
Indicates that customs and immigration control services are present or provided at a given location or facility.
- 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_69a2e80111fc8190961d5b7c6154123f |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ecbf0650819080753815ca280eec |
completed | Feb. 28, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69a2e971a3a481909e6b075f25dd234a |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.