Triple
T16457161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Doe (Se7en) |
E399711
|
entity |
| Predicate | turnsHimselfInTo |
P122856
|
FINISHED |
| Object | police |
—
|
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: police | Statement: [John Doe (Se7en), turnsHimselfInTo, police]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: turnsHimselfInTo Context triple: [John Doe (Se7en), turnsHimselfInTo, police]
-
A.
takesFormOf
Indicates that one entity assumes, manifests, or is expressed in the shape, structure, or configuration of another entity.
-
B.
wasTransformedBy
Indicates that an entity has undergone a change of state, form, or condition as the result of an action, process, or agent.
-
C.
turnedInformant
Indicates that an individual who was previously involved with a group or activity has begun secretly providing information about it to authorities or another opposing party.
-
D.
calledHimself
Indicates that a person referred to or identified himself using a particular name, title, or description.
-
E.
bodyTransformedInto
Indicates that one entity’s physical form is changed or converted into another specified form or entity.
- F. None of above. chosen
Provenance (4 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_69d87f2dac988190b74d6e185fa88ba4 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32d7dfd188190b03e9b4151a4d3d8 |
completed | April 18, 2026, 7:06 a.m. |
| PD | Predicate disambiguation | batch_69e227048d608190a4205eae3117629a |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24556c1348190902a4d116c3137d9 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:10 a.m.