Triple
T3493470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscow Armistice requirements |
E73790
|
entity |
| Predicate | typeOfDemand |
P36000
|
FINISHED |
| Object | military |
—
|
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: military | Statement: [Moscow Armistice requirements, typeOfDemand, military]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfDemand Context triple: [Moscow Armistice requirements, typeOfDemand, military]
-
A.
typeOfRequirement
chosen
Indicates that one requirement is classified as a specific kind or category of another, more general requirement.
-
B.
demand
Indicates that one entity requests or insists that another entity provide something or perform an action, often with an expectation of compliance.
-
C.
demands
Indicates that one entity insists that another entity provide something or take a specific action, typically with authority or urgency.
-
D.
demanded
Indicates that one entity forcefully or insistently requested something from another entity.
-
E.
typeOfSupport
Indicates the kind or category of assistance, help, or backing provided in a given context.
- 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_69ad85cdb6e48190a335d412b9194ed8 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbbad51648190b756ad621d6d7df0 |
completed | March 8, 2026, 6:10 p.m. |
| PD | Predicate disambiguation | batch_69adae0b34908190b2bb5766a2231f7a |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:18 p.m.