Triple
T36678287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Constables |
E905602
|
entity |
| Predicate | canTransferBetween |
P97562
|
FINISHED |
| Object | different UK police forces |
—
|
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: different UK police forces | Statement: [Special Constables, canTransferBetween, different UK police forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canTransferBetween Context triple: [Special Constables, canTransferBetween, different UK police forces]
-
A.
transferBetween
chosen
Indicates a movement or handover of something from one entity to another, typically changing its location, ownership, or control between them.
-
B.
allowsTransferTo
Indicates that one entity permits or enables the transfer of something (such as rights, funds, or data) to another specified entity.
-
C.
transferType
Indicates the specific method or category of how something is transferred from one entity to another.
-
D.
transfersAvailableAt
Indicates that one entity offers or supports the ability to transfer to another service, route, or mode at a specified location or context.
-
E.
hasTransfer
Indicates a relationship where something is moved or conveyed from one entity or location to another.
- 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_69f76e7011dc819082b324f18b756a1b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c7a487408190b3a5ee144e651046 |
completed | May 3, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69f7c4796ebc819084a0dc08505e5f14 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:12 p.m.