Triple
T24176476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Endurance Expedition |
E599295
|
entity |
| Predicate | expeditionSurgeon |
P155588
|
FINISHED |
| Object | Alexander Macklin |
—
|
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: Alexander Macklin | Statement: [Endurance Expedition, expeditionSurgeon, Alexander Macklin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expeditionSurgeon Context triple: [Endurance Expedition, expeditionSurgeon, Alexander Macklin]
-
A.
expeditionMemberOf
Indicates that an entity participates as a member in a specific expedition.
-
B.
visitingExpeditionCrew
Indicates a relationship where a crew is temporarily present at a location or facility as a visiting expedition team, rather than being part of the resident or primary crew.
-
C.
expeditionShip
Indicates a relationship where a ship is designated or used specifically for conducting an expedition or exploratory mission.
-
D.
expeditionPatron
Indicates that an entity financially supports or sponsors an expedition or exploratory venture.
-
E.
expedition4Commander
Indicates that the subject served as the commander of the fourth expedition.
- 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_69e288cca05481908faeb1563711114a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f27a753ca8819095706970d368f762 |
completed | April 29, 2026, 9:39 p.m. |
Created at: April 17, 2026, 11:34 p.m.