Triple
T31207834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Murder at Carthage Jail |
E795649
|
entity |
| Predicate | hasDetainedPerson |
P105577
|
FINISHED |
| Object | Joseph Smith |
—
|
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: Joseph Smith | Statement: [Murder at Carthage Jail, hasDetainedPerson, Joseph Smith]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDetainedPerson Context triple: [Murder at Carthage Jail, hasDetainedPerson, Joseph Smith]
-
A.
coDetainee
Indicates that two or more individuals are detained or imprisoned together in the same facility or under the same custodial authority.
-
B.
detainsUnder
chosen
Indicates that one entity holds another in custody or confinement under a specific legal authority, provision, or condition.
-
C.
detainedBy
Indicates that an entity is being held in custody or confinement by another entity, typically an authority or controlling party.
-
D.
leaderDetained
Indicates that a leader has been taken into custody or otherwise restrained by an authority, preventing them from acting freely.
-
E.
detainedFor
Indicates that one entity is being held in custody or confinement because of, or as a consequence of, another entity (such as a reason, charge, or event).
- 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_69f224d8c6608190b7882466521f62be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
Created at: April 29, 2026, 9:09 p.m.