Triple
T25353937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andrée balloon expedition 1897 |
E635768
|
entity |
| Predicate | crashLandingLocation |
P145200
|
FINISHED |
| Object | Arctic pack ice |
—
|
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: Arctic pack ice | Statement: [Andrée balloon expedition 1897, crashLandingLocation, Arctic pack ice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crashLandingLocation Context triple: [Andrée balloon expedition 1897, crashLandingLocation, Arctic pack ice]
-
A.
crashLandedOn
Indicates that one entity made an unintended or uncontrolled landing onto the surface or location represented by another entity.
-
B.
crashLandsIn
chosen
Indicates that an entity descends and lands in a location or object in an uncontrolled or damaging manner.
-
C.
landedNear
Indicates that one entity has come to rest on a surface or location in close proximity to another specified entity or reference point.
-
D.
planeCrashLocation
Indicates the location where a plane crash occurred.
-
E.
landingPlace
Indicates the location or surface where something or someone comes down to rest after moving through the air or space.
- 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_69e75a9ac5d881909387ed766e20cd47 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f49dfedae88190a02f10196ef45ffa |
completed | May 1, 2026, 12:35 p.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
Created at: April 21, 2026, 1:34 p.m.