Triple
T3379446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Decourcy Ward |
E71145
|
entity |
| Predicate | worksAgainst |
P47485
|
FINISHED |
| Object | corrupt police practices |
—
|
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: corrupt police practices | Statement: [Decourcy Ward, worksAgainst, corrupt police practices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worksAgainst Context triple: [Decourcy Ward, worksAgainst, corrupt police practices]
-
A.
worksTo
Indicates that one entity performs work or exerts effort in order to achieve, support, or contribute to another entity or outcome.
-
B.
worksFor
Indicates that one entity is employed by or performs work on behalf of another entity, typically an organization or individual.
-
C.
worksAs
Indicates that an entity performs the role, job, or occupation specified by another entity.
-
D.
worksWith
Indicates that two entities collaborate or perform tasks together in a shared work-related context.
-
E.
workBy
Indicates that a work (such as a creation, product, or result) is produced, authored, or created by a particular agent 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_69ad85a7f80c8190a05e43013f298942 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb2ec38d88190be8c824daeca5ab6 |
completed | March 8, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69ada434bae48190a77ea37f9274ad8f |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada52716ec81908e89688a81039394 |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:14 p.m.