Triple
T23806708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Parks Constabulary |
E589727
|
entity |
| Predicate | officersSwornAs |
P16363
|
FINISHED |
| Object | constables |
—
|
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: constables | Statement: [Royal Parks Constabulary, officersSwornAs, constables]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officersSwornAs Context triple: [Royal Parks Constabulary, officersSwornAs, constables]
-
A.
swornInOn
Indicates that an individual formally assumes an office, role, or duty by taking an official oath on a specified date, occasion, or object.
-
B.
officersServeAs
Indicates that certain individuals hold and perform the role or duties of officers within a particular organization or context.
-
C.
officersAre
chosen
Indicates that certain individuals hold the role or position of officers within a specified group, organization, or context.
-
D.
sworeInAs
Indicates that one entity formally administered or participated in the official oath-taking that installed another entity into an office, role, or position.
-
E.
officersHave
Indicates that certain individuals hold official positions or roles within a specified organization or 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_69e25d19fecc8190a5cf39bbb18d5d7f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c75206a88190b6e35da289471c27 |
completed | April 29, 2026, 8:54 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:56 p.m.