Triple
T33357095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Endurance (ship) |
E854101
|
entity |
| Predicate | ownerAtExpedition |
P155592
|
FINISHED |
| Object | Ernest Shackleton |
—
|
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: Ernest Shackleton | Statement: [Endurance (ship), ownerAtExpedition, Ernest Shackleton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownerAtExpedition Context triple: [Endurance (ship), ownerAtExpedition, Ernest Shackleton]
-
A.
ownerDuringExpedition
chosen
Indicates that one entity is the owner of another entity specifically for the duration of a particular expedition or journey.
-
B.
usedByExpedition
Indicates that something (such as an object, resource, or method) is utilized or employed by an expedition in the course of its activities.
-
C.
roleInExpedition
Indicates the specific function, duty, or position an entity holds within the context of a particular expedition.
-
D.
expeditionMemberOf
Indicates that an entity participates as a member in a specific expedition.
-
E.
issExpedition
Indicates an expedition or mission associated with the International Space Station (ISS).
- 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_69f3496acbc8819099fd0305ecc42080 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: May 1, 2026, 1:34 a.m.