Triple
T24764138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carsten Borchgrevink |
E619532
|
entity |
| Predicate | expeditionSite |
P48499
|
FINISHED |
| Object | Cape Adare |
—
|
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: Cape Adare | Statement: [Carsten Borchgrevink, expeditionSite, Cape Adare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expeditionSite Context triple: [Carsten Borchgrevink, expeditionSite, Cape Adare]
-
A.
explorationSiteOf
Indicates that a location or site is the place where a particular exploration activity, mission, or project is conducted or associated.
-
B.
discoveryExpedition
Indicates an expedition undertaken with the purpose of exploring or discovering new places, phenomena, or information.
-
C.
expeditionEvent
Indicates an event or occurrence that takes place as part of, or in direct connection with, an expedition.
-
D.
notableExpeditionLocation
chosen
Indicates that a location is a significant or primary place associated with a particular expedition.
-
E.
expeditionCarpenter
Indicates that one entity serves as the carpenter responsible for construction or repair work within an expedition involving another entity.
- 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_69e2fabbea94819092ed41348909622f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f410a4591c81909f918efd84a1f6f6 |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:28 a.m.