Triple
T9877256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | QOR |
E240101
|
entity |
| Predicate | hasReserveRole |
P6239
|
FINISHED |
| Object | augment regular forces in operations |
—
|
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: augment regular forces in operations | Statement: [QOR, hasReserveRole, augment regular forces in operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReserveRole Context triple: [QOR, hasReserveRole, augment regular forces in operations]
-
A.
hasLegalRole
Indicates that an entity holds a specific legal capacity, status, or function in relation to another entity or context.
-
B.
hasGlobalRole
Indicates that an entity holds a role or permission set that applies across an entire system or domain, rather than being limited to a specific scope or context.
-
C.
hasAuxiliaryRole
chosen
Indicates that an entity serves in a supporting or secondary capacity to another entity or primary role.
-
D.
hasCustodyRole
Indicates that one entity holds a specific custodial responsibility or role in relation to another entity.
-
E.
hasCapitalOwnerRole
Indicates that an entity holds the role or status of owning capital in relation to another entity or asset.
- 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_69ca84e8a0788190b9061811d50fd554 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb411fc78819082c52ae4233a6550 |
completed | April 2, 2026, 12:10 a.m. |
| PD | Predicate disambiguation | batch_69cd1d810ed48190a252b70e9390c8f3 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:37 p.m.