Triple
T11807903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tommy Caldwell |
E280795
|
entity |
| Predicate | kidnappingIncident |
P97594
|
FINISHED |
| Object | kidnapped in Kyrgyzstan in 2000 during a climbing trip |
—
|
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: kidnapped in Kyrgyzstan in 2000 during a climbing trip | Statement: [Tommy Caldwell, kidnappingIncident, kidnapped in Kyrgyzstan in 2000 during a climbing trip]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kidnappingIncident Context triple: [Tommy Caldwell, kidnappingIncident, kidnapped in Kyrgyzstan in 2000 during a climbing trip]
-
A.
wasKidnapped
Indicates that an entity was forcibly taken and held against their will by another entity.
-
B.
featuresChildAbduction
Indicates that an event, situation, or narrative involves the abduction or kidnapping of a child as a central or notable element.
-
C.
abductedBy
Indicates that an entity has been forcibly taken or carried away by another entity against their will.
-
D.
abductedFrom
Indicates that an entity was forcibly taken away or kidnapped from a specified location or source.
-
E.
countryOfAbduction
chosen
Indicates the country in which the abduction of the referenced entity took place.
- 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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a658f918819092c2db05fe2ab0ce |
completed | April 10, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69d8a24e9a088190aff7932d1ff93dbf |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.