Triple
T25353938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andrée balloon expedition 1897 |
E635768
|
entity |
| Predicate | finalCampLocation |
P63873
|
FINISHED |
| Object | Kvitøya |
—
|
NE NERFINISHED |
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: Kvitøya | Statement: [Andrée balloon expedition 1897, finalCampLocation, Kvitøya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalCampLocation Context triple: [Andrée balloon expedition 1897, finalCampLocation, Kvitøya]
-
A.
finalsLocation
Indicates the place where the final stage or concluding event of something (such as a competition or process) takes place.
-
B.
campLocation
chosen
Indicates the place or area where a camp is set up or located.
-
C.
formerFinishLocation
Indicates that an entity was previously the finish location of an event or activity, but no longer holds that status.
-
D.
finalConcertLocation
Indicates the location where a concert or performance ultimately takes place, especially after any changes or planning stages.
-
E.
finalWentTo
Indicates that an entity ultimately went to or arrived at a particular location as the final destination in a sequence of movements or places visited.
- 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_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 21, 2026, 1:34 p.m.