Triple
T30734618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nick Sobotka |
E782514
|
entity |
| Predicate | turnsInformantFor |
P87074
|
FINISHED |
| Object | Baltimore Police Department |
—
|
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: Baltimore Police Department | Statement: [Nick Sobotka, turnsInformantFor, Baltimore Police Department]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: turnsInformantFor Context triple: [Nick Sobotka, turnsInformantFor, Baltimore Police Department]
-
A.
turnedInformant
chosen
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.
-
B.
turnsHimselfInTo
Indicates that a person voluntarily surrenders or reports himself to an authority, typically law enforcement or another official body.
-
C.
turnsIn
Indicates that an entity submits or hands over something, typically work or an item, to another party or authority.
-
D.
turns
Indicates a change in orientation, direction, or state initiated by one entity affecting itself or another entity.
-
E.
usedInforms
Indicates that one entity utilizes information from another entity to guide or shape its own actions, decisions, or outputs.
- 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:37 p.m.