Triple
T530430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Police |
E12210
|
entity |
| Predicate | operatedUnderCommandOf |
P6842
|
FINISHED |
| Object | German authorities |
—
|
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: German authorities | Statement: [Blue Police, operatedUnderCommandOf, German authorities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedUnderCommandOf Context triple: [Blue Police, operatedUnderCommandOf, German authorities]
-
A.
commandedIn
Indicates that one entity held a position of command or leadership within a specified context, such as a battle, operation, or organization.
-
B.
commandedBy
Indicates that one entity holds authoritative control or issues orders over another entity.
-
C.
isCommandedIn
chosen
Indicates that an entity is under the authority or control of another entity within a specific context, such as a mission, operation, or organizational structure.
-
D.
commander
Indicates that one entity holds authoritative military or organizational control over another entity or group.
-
E.
hasCommander
Indicates that one entity serves as the commanding officer or leader of 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_69a4933208e88190891f5debab1b776d |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4985e51908190a34aa82ea9dbee1e |
completed | March 1, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69a494b257108190a537dffbb9d621b5 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.