Triple
T35289729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steven Stayner |
E1019187
|
entity |
| Predicate | heldInCaptivityFor |
P50041
|
FINISHED |
| Object | approximately 7 years |
—
|
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: approximately 7 years | Statement: [Steven Stayner, heldInCaptivityFor, approximately 7 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldInCaptivityFor Context triple: [Steven Stayner, heldInCaptivityFor, approximately 7 years]
-
A.
periodOfCaptivity
chosen
Indicates a time span during which an entity is held in captivity or confinement.
-
B.
heldCaptive
Indicates that one entity is being forcibly confined or restrained by another, preventing their freedom of movement or escape.
-
C.
heldTitleWhileInCaptivity
Indicates that an entity continued to hold a specific title or position during a period when they were in captivity.
-
D.
captivityEnd
Indicates the point in time or event at which an entity’s period of captivity or confinement comes to an end.
-
E.
heldHostagesFor
Indicates that one party unlawfully detained another party or parties as hostages for a period of time, typically to exert pressure or gain leverage.
- 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_69f76de6d39c8190bb11342e4b91ff2b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79012e2e481908c587ff189b3deb3 |
completed | May 3, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.