Triple
T4918451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brigadier General |
E110402
|
entity |
| Predicate | officerCategory |
P60021
|
FINISHED |
| Object | commissioned officer |
—
|
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: commissioned officer | Statement: [Brigadier General, officerCategory, commissioned officer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officerCategory Context triple: [Brigadier General, officerCategory, commissioned officer]
-
A.
officersAre
Indicates that certain individuals hold the role or position of officers within a specified group, organization, or context.
-
B.
policeRank
Indicates that one entity holds a specific rank or position within a police organization relative to another entity.
-
C.
typeOfLawEnforcement
Indicates that one entity is a specific kind or category of law enforcement associated with another entity.
-
D.
isOfficerOf
Indicates that one entity holds an official position, role, or office within another entity (such as an organization, group, or institution).
-
E.
policeCharacter
Indicates that one entity serves as a police officer or law-enforcement figure in relation to another entity.
- F. None of above. chosen
Provenance (4 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_69bd4413f9908190afcff44d7929cc4c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6fa8be048190892dfaba4d865ee1 |
completed | March 20, 2026, 4:02 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3421588190ab08e92b9558042e |
completed | March 20, 2026, 3:48 p.m. |
| PDg | Predicate description generation | batch_69bd6e482984819087124216738f1e29 |
completed | March 20, 2026, 3:56 p.m. |
Created at: March 20, 2026, 1:29 p.m.