Triple
T20841318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sergeant of Police |
E513108
|
entity |
| Predicate | commandedGroup |
P19105
|
FINISHED |
| Object | Cornish policemen |
—
|
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: Cornish policemen | Statement: [Sergeant of Police, commandedGroup, Cornish policemen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandedGroup Context triple: [Sergeant of Police, commandedGroup, Cornish policemen]
-
A.
commandOf
chosen
Indicates that one entity holds authoritative control or leadership over another, typically in a military, organizational, or hierarchical context.
-
B.
commandedBy
Indicates that one entity holds authoritative control or issues orders over another entity.
-
C.
commandedIn
Indicates that one entity held a position of command or leadership within a specified context, such as a battle, operation, or organization.
-
D.
commandedTo
Indicates that one entity has issued an order or directive for another entity to perform a specific action or fulfill a particular duty.
-
E.
ethnicGroupOfCommand
Indicates that a particular ethnic group is associated with, or has control over, a specific command or military/organizational leadership structure.
- 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_69e0b4cf62a88190bbf92351e9e57259 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c34b17b88190b3290bd5100ad2ad |
completed | April 21, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a1f4f48190aa9fb4ef8f8aea5a |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:43 p.m.