Triple
T7048103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Territorial Force |
E163693
|
entity |
| Predicate | voluntaryNature |
P2797
|
FINISHED |
| Object | volunteer force |
—
|
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: volunteer force | Statement: [Territorial Force, voluntaryNature, volunteer force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voluntaryNature Context triple: [Territorial Force, voluntaryNature, volunteer force]
-
A.
voluntary
chosen
Indicates that an action or relationship is undertaken by an entity by free choice, without coercion or obligation.
-
B.
volunteeredFor
Indicates that an entity willingly offered their time or services to support or participate in an activity, cause, or organization.
-
C.
nonVolatile
Indicates that the associated entity or state does not change, disappear, or lose its value when power is removed or over time.
-
D.
volunteerOrConscript
Indicates that an entity participates in a role, service, or activity either by choosing to do so voluntarily or by being compelled or drafted into it.
-
E.
nonGovernmental
Indicates that an entity, action, or relationship is not associated with, controlled by, or part of a government or governmental body.
- 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_69c6885f598c8190b6b6495c59d8d962 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e4a3c36c819080942c59f1830ae8 |
completed | March 27, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bb602081908bfa6186a1f5a4b4 |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:37 p.m.