Triple
T14776727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Territorial Army |
E347279
|
entity |
| Predicate | mobilizationType |
P34132
|
FINISHED |
| Object | called up when needed |
—
|
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: called up when needed | Statement: [Territorial Army, mobilizationType, called up when needed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mobilizationType Context triple: [Territorial Army, mobilizationType, called up when needed]
-
A.
mobilizationMethod
Indicates the method or process by which resources, people, or assets are organized and activated for a particular purpose or operation.
-
B.
mobilization
chosen
Indicates the process by which entities are organized, activated, or assembled to take coordinated action or move into a state of readiness.
-
C.
mobilizationUse
Indicates the use or deployment of resources, personnel, or assets as part of a mobilization effort.
-
D.
mobilizes
Indicates initiating or organizing movement, action, or deployment of entities toward a specific goal or task.
-
E.
mobilizationAuthority
Indicates the entity that has the formal power or responsibility to initiate, direct, or authorize the mobilization of resources, personnel, or assets.
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec817c39081909b08a0ffdfce9936 |
completed | April 14, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69de8c02e5c08190943c27594026faf7 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:31 a.m.