Triple
T6943351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 89th Military Police Brigade |
E160731
|
entity |
| Predicate | associatedBranchColor |
P17726
|
FINISHED |
| Object | green |
—
|
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: green | Statement: [89th Military Police Brigade, associatedBranchColor, green]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedBranchColor Context triple: [89th Military Police Brigade, associatedBranchColor, green]
-
A.
uniformBranchColor
Indicates that all branches of the referenced entity share the same color.
-
B.
secondaryBranchColor
Indicates the color assigned to a secondary or subordinate branch in relation to a primary branch.
-
C.
serviceBranchColor
chosen
Indicates the specific color associated with a particular branch of service (e.g., military or organizational branch) as its identifying or representative color.
-
D.
associatedColour
Indicates that one entity is linked to another as its characteristic or representative colour.
-
E.
affectedBranch
Indicates that one entity is a branch that is impacted or influenced by the state or actions associated with 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_69c6884f3db4819080ad65da69386206 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e0c74fe48190aeaa018631e52ef6 |
completed | March 27, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bd5a388190a57a96d925696ff6 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:28 p.m.