Triple
T29944076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 343rd Brigade |
E760583
|
entity |
| Predicate | hasMilitaryUnitSize |
P180442
|
FINISHED |
| Object | brigade |
—
|
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: brigade | Statement: [343rd Brigade, hasMilitaryUnitSize, brigade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMilitaryUnitSize Context triple: [343rd Brigade, hasMilitaryUnitSize, brigade]
-
A.
militarySize
Indicates the total number of personnel in a military force, typically including active-duty members and sometimes reserves.
-
B.
commandingForceSize
Indicates the size or magnitude of the military or organizational force that is exercising command or control in a given context.
-
C.
eliteUnitSize
Indicates the number of members that make up an elite or specially designated unit.
-
D.
militaryUnitOf
Indicates that one entity is a military unit that belongs to, is part of, or is under the command or organizational structure of another entity.
-
E.
restrictedArmySizeOf
Indicates that one entity imposes a limitation or cap on the allowable size of another entity’s army.
- 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_69f22463f3648190a603c3ff305c660b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
| PDg | Predicate description generation | batch_69f74061c440819080434155c2d60341 |
completed | May 3, 2026, 12:32 p.m. |
Created at: April 29, 2026, 6:23 p.m.