Triple
T3932640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 27th Armoured Brigade |
E90829
|
entity |
| Predicate | specialRole |
P52608
|
FINISHED |
| Object | armoured assault support |
—
|
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: armoured assault support | Statement: [27th Armoured Brigade, specialRole, armoured assault support]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specialRole Context triple: [27th Armoured Brigade, specialRole, armoured assault support]
-
A.
secretRole
Indicates that an entity holds a role or function that is intentionally hidden or not publicly disclosed within a given context.
-
B.
possibleRole
Indicates that an entity is capable of or eligible to serve in a particular role or function in a given context.
-
C.
specialAppearance
Indicates that an entity makes a notable or exceptional appearance distinct from its usual or regular presence.
-
D.
effectiveRole
Indicates the functional role or capacity an entity actually performs or holds in a given context, regardless of its formal or nominal designation.
-
E.
specialValue
Indicates that an entity possesses a distinguished or exceptional value compared to typical or default values in the given context.
- 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_69aed95f26e0819094b0e71974543a19 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeedaaf3c881909539831bf3a8bf10 |
completed | March 9, 2026, 3:56 p.m. |
| PD | Predicate disambiguation | batch_69aee7625ad4819097e4e8a168c19274 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aeed3260cc8190bf294bdab507b1f9 |
completed | March 9, 2026, 3:54 p.m. |
Created at: March 9, 2026, 3:23 p.m.