Triple
T34822945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Faith Lehane |
E1003835
|
entity |
| Predicate | turnsHerselfIn |
P122856
|
FINISHED |
| Object | to 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: to police | Statement: [Faith Lehane, turnsHerselfIn, to police]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: turnsHerselfIn Context triple: [Faith Lehane, turnsHerselfIn, to police]
-
A.
turnsHimselfInTo
chosen
Indicates that a person voluntarily surrenders or reports himself to an authority, typically law enforcement or another official body.
-
B.
confessedTo
Indicates that one entity admitted guilt or revealed the truth about an action, wrongdoing, or secret to another entity.
-
C.
turnedInToAuthorities
Indicates that one entity surrendered or delivered another entity to law enforcement or official authorities.
-
D.
typeOfSurrender
Indicates the specific manner or category of surrender that characterizes how one party yields or gives up to another.
-
E.
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.
- 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_69f76db717088190811b4e744610f37d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77adeac048190bbe22f1b663009d5 |
completed | May 3, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69f7795b1abc8190823664d1caa94649 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 4 p.m.