Triple
T25353936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andrée balloon expedition 1897 |
E635768
|
entity |
| Predicate | launchArchipelago |
P159110
|
FINISHED |
| Object | Svalbard |
—
|
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: Svalbard | Statement: [Andrée balloon expedition 1897, launchArchipelago, Svalbard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchArchipelago Context triple: [Andrée balloon expedition 1897, launchArchipelago, Svalbard]
-
A.
locatedInArchipelago
Indicates that one place or geographic entity is situated within or is part of a specific archipelago.
-
B.
includesArchipelago
Indicates that one geographic entity contains or encompasses an archipelago within its area or jurisdiction.
-
C.
archipelagoType
Indicates the specific kind or classification of an archipelago based on its characteristics or formation.
-
D.
archipelagoStatus
Indicates that an entity has the status or classification of being an archipelago, typically denoting a group or chain of islands considered as a single geographic or administrative unit.
-
E.
hasIslandArc
Indicates that one geographic or geological entity possesses or is associated with an island arc feature.
- F. None of above. chosen
Provenance (4 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_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 21, 2026, 1:34 p.m.