Triple
T22589414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1913 Denali expedition |
E564899
|
entity |
| Predicate | coLedBy |
P68732
|
FINISHED |
| Object | Harry P. Karstens |
—
|
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: Harry P. Karstens | Statement: [1913 Denali expedition, coLedBy, Harry P. Karstens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coLedBy Context triple: [1913 Denali expedition, coLedBy, Harry P. Karstens]
-
A.
coLeaderWith
Indicates that two or more entities share a joint leadership role or position with equal or comparable authority.
-
B.
collaborationLedBy
chosen
Indicates that a collaborative effort or project is directed, coordinated, or overseen by a specific leading entity.
-
C.
coalitionLed
Indicates that one entity serves as the primary leader or organizer of a coalition composed of multiple entities.
-
D.
leadingOrgan
Indicates that one entity serves as the primary or most responsible organizing body or authority for another entity or activity.
-
E.
responseLedBy
Indicates that a particular response, initiative, or action is directed, coordinated, or overseen by a specified leading 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_69e245836014819091b91ed3074742a3 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1615f63788190acf776b313f0794a |
completed | April 29, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_69ee627be4248190889a88764624e174 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 2:48 p.m.