Triple
T1841979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2nd Armoured Brigade |
E41195
|
entity |
| Predicate | hasSize |
P34032
|
FINISHED |
| Object | brigade strength |
—
|
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 strength | Statement: [2nd Armoured Brigade, hasSize, brigade strength]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSize Context triple: [2nd Armoured Brigade, hasSize, brigade strength]
-
A.
hasMinimumSize
Indicates that an entity meets or exceeds a specified minimum size threshold.
-
B.
hasBoardSize
Indicates that an entity is associated with a board whose dimensions or overall size are specified.
-
C.
hasRelativeSize
Indicates that one entity’s size is being compared to another entity’s size, expressing a relative rather than absolute magnitude.
-
D.
hasHeight
Indicates that one entity possesses a specific vertical measurement or stature.
-
E.
includesSizeRange
Indicates that one entity specifies or covers a particular range of sizes associated with 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_69a88648cd44819093303206d96d76ad |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafdb0d2c8190a67f584e67979fa3 |
completed | March 7, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69abb32a8d548190a231c7c2ce276a5e |
completed | March 7, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:33 p.m.