Triple
T22402439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 4th Battalion, The Rifles |
E553792
|
entity |
| Predicate | equipmentEmphasis |
P148025
|
FINISHED |
| Object | light equipment |
—
|
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: light equipment | Statement: [4th Battalion, The Rifles, equipmentEmphasis, light equipment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: equipmentEmphasis Context triple: [4th Battalion, The Rifles, equipmentEmphasis, light equipment]
-
A.
recommendedEquipment
Indicates that one entity suggests or endorses another entity as suitable equipment to be used in a particular context or activity.
-
B.
equipmentIncludes
Indicates that one entity contains, comprises, or has as part of its set of items a specified piece or set of equipment.
-
C.
equipmentOption
Indicates that a particular piece or configuration of equipment is available or selected as an option in a given context.
-
D.
usesEquipment
Indicates that an entity employs or operates a particular piece of equipment to perform an action or fulfill a function.
-
E.
equipmentProvider
Indicates that one entity supplies or makes available equipment for use by 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_69e11e4da7048190b4387d422a9a0de5 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f158b565c48190b0f6c19f17995b40 |
completed | April 29, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69e8989495bc81909d2699fce5992e28 |
completed | April 22, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69e8aa39e3388190b659d59948ebf3e6 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:46 p.m.