Triple
T14768468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian Antarctic Expedition 1910–1912 |
E347065
|
entity |
| Predicate | noMemberDiedOnMainPolarJourney |
P33525
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Norwegian Antarctic Expedition 1910–1912, noMemberDiedOnMainPolarJourney, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: noMemberDiedOnMainPolarJourney Context triple: [Norwegian Antarctic Expedition 1910–1912, noMemberDiedOnMainPolarJourney, true]
-
A.
diedOnJourneyBetween
Indicates that an entity died while traveling between two specified locations or points in a journey.
-
B.
diedDuringExpeditionOn
Indicates that an entity died while participating in a specific expedition that took place on a given date.
-
C.
fateOfMembers
chosen
Indicates the outcome, destiny, or final status experienced by the members of a group or collection.
-
D.
possiblyDiedIn
Indicates that an entity is believed or suspected to have died in a particular place, but this is uncertain or not definitively confirmed.
-
E.
hasNotableExpedition
Indicates that an entity is associated with a significant or noteworthy expedition, journey, or exploratory mission.
- 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_69d822e8896c819091169882f9b20486 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec81236f081908063bb4350b7b985 |
completed | April 14, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69de8c02e5c08190943c27594026faf7 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:30 a.m.