Triple
T28043516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mortal Thoughts |
E708611
|
entity |
| Predicate | hasPoliceInterrogationFrame |
P34821
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Mortal Thoughts, hasPoliceInterrogationFrame, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPoliceInterrogationFrame Context triple: [Mortal Thoughts, hasPoliceInterrogationFrame, true]
-
A.
hasCrimeScene
Indicates that a particular location or setting is the site where a specific crime occurred or was discovered.
-
B.
hasBeenArrestedBy
Indicates that an entity has been taken into custody or formally apprehended by another entity, typically a law enforcement authority.
-
C.
wasQuestionedBefore
Indicates that one entity was subjected to questioning at an earlier time than another entity.
-
D.
interrogationMethod
chosen
Indicates the technique or approach used by one party to question or extract information from another.
-
E.
hasPolicePartner
Indicates that one entity has another entity as its partner in a police or law-enforcement context.
- 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_69ef9b6cf538819094a633ffa67afec1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: April 27, 2026, 8:27 p.m.