Triple
T16101015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jimmy Shaker |
E390619
|
entity |
| Predicate | usesPositionTo |
P49236
|
FINISHED |
| Object | manipulate kidnapping investigation |
—
|
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: manipulate kidnapping investigation | Statement: [Jimmy Shaker, usesPositionTo, manipulate kidnapping investigation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPositionTo Context triple: [Jimmy Shaker, usesPositionTo, manipulate kidnapping investigation]
-
A.
positionUse
chosen
Indicates how a particular position or role is utilized or functionally applied within a given context.
-
B.
appliesToPosition
Indicates that something (such as a rule, condition, or attribute) is relevant or applicable to a specific position or role.
-
C.
supportsPosition
Indicates that one entity endorses, upholds, or provides backing for the stance, viewpoint, or role represented by another entity.
-
D.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
E.
isPositionOf
Indicates that one entity represents the spatial or organizational position or location of another entity.
- 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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1ff68686481909517eed4266729ca |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e182804208819087f35307cd6e4103 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5 a.m.