Triple
T8948447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert Knox |
E213282
|
entity |
| Predicate | causeOfCaptivity |
P76310
|
FINISHED |
| Object | detained by forces of the King of Kandy |
—
|
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: detained by forces of the King of Kandy | Statement: [Robert Knox, causeOfCaptivity, detained by forces of the King of Kandy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfCaptivity Context triple: [Robert Knox, causeOfCaptivity, detained by forces of the King of Kandy]
-
A.
periodOfCaptivity
Indicates a time span during which an entity is held in captivity or confinement.
-
B.
captivityEnd
Indicates the point in time or event at which an entity’s period of captivity or confinement comes to an end.
-
C.
captivesTaken
chosen
Indicates that one entity has taken another entity or group into captivity, holding them against their will.
-
D.
heldCaptive
Indicates that one entity is being forcibly confined or restrained by another, preventing their freedom of movement or escape.
-
E.
prisonerOf
Indicates that one entity is held in custody or confinement by another entity, typically under legal or authoritative control.
- 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_69ca839843408190a39069a029a89f15 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6709c7a48190ab503083a1d6a29f |
completed | April 1, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed5267c8190a43feb2a2f3df1ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 6:59 p.m.