Triple
T23488725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SVPNPA |
E570611
|
entity |
| Predicate | trainingCovers |
P23937
|
FINISHED |
| Object | policing |
—
|
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: policing | Statement: [SVPNPA, trainingCovers, policing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trainingCovers Context triple: [SVPNPA, trainingCovers, policing]
-
A.
trainingUnder
Indicates that one entity is receiving instruction, guidance, or mentorship from another, typically in a subordinate or apprentice-like capacity.
-
B.
providesTrainingFor
Indicates that one entity delivers or conducts training activities intended to develop the skills or knowledge of another entity.
-
C.
trainingSupport
Indicates that one entity provides assistance, resources, or facilitation to help another entity conduct or participate in training activities.
-
D.
training
Indicates that one entity is teaching, coaching, or otherwise helping another entity acquire or improve a skill, behavior, or capability.
-
E.
trainingComponent
chosen
Indicates that one entity functions as a training-related part, module, or element within a larger training process or system involving 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_69e245b0b01481908f636939bedd804c |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a7dae8cc8190bf74d1bdb0fc6c60 |
completed | April 29, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:04 p.m.