Triple
T35074188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Active Forces |
E1011964
|
entity |
| Predicate | mayBeAugmentedBy |
P17547
|
FINISHED |
| Object | Reserve Forces during mobilization |
—
|
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: Reserve Forces during mobilization | Statement: [Active Forces, mayBeAugmentedBy, Reserve Forces during mobilization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeAugmentedBy Context triple: [Active Forces, mayBeAugmentedBy, Reserve Forces during mobilization]
-
A.
canBeAugmentedWith
chosen
Indicates that one entity is capable of being enhanced, expanded, or supplemented by another entity.
-
B.
mayBeExtended
Indicates that something has the potential or option to be lengthened in duration, scope, or size beyond its current or initial limits.
-
C.
mayExtendTo
Indicates that something has the potential or permission to reach, continue, or be applied up to a specified limit, scope, or boundary.
-
D.
mayAlsoInclude
Indicates that something can optionally contain or encompass additional elements beyond those primarily specified.
-
E.
mayBeModifiedBy
Indicates that an entity has the potential to be altered, changed, or updated by another entity or process.
- 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_69f76dd193108190af2528186f25b72a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:01 p.m.