Triple
T14244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phoney War |
E284
|
entity |
| Predicate | characteristic |
P274
|
FINISHED |
| Object | limited skirmishes and patrols |
—
|
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: limited skirmishes and patrols | Statement: [Phoney War, characteristic, limited skirmishes and patrols]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characteristic Context triple: [Phoney War, characteristic, limited skirmishes and patrols]
-
A.
demographicsCharacteristic
Indicates that one entity serves as a demographic attribute or characteristic (such as age, gender, ethnicity, etc.) that describes or classifies another entity.
-
B.
describes
Indicates that one entity provides an explanation, representation, or account of another entity or concept.
-
C.
category
Indicates that one entity is classified as a member or type within the grouping or class defined by another entity.
-
D.
hasCharacteristic
chosen
Indicates that an entity possesses, exhibits, or is defined by a particular attribute, feature, or quality.
-
E.
significance
Indicates that one entity holds particular importance, influence, or meaningful impact in relation to another entity or 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_69a23d7ad88c8190bffe8ab091d86642 |
completed | Feb. 28, 2026, 12:57 a.m. |
| NER | Named-entity recognition | batch_69a240b249788190af8dbf7e80e9c91b |
completed | Feb. 28, 2026, 1:11 a.m. |
| PD | Predicate disambiguation | batch_69a23feae8c481908d8c50faac01fc5c |
completed | Feb. 28, 2026, 1:07 a.m. |
Created at: Feb. 28, 2026, 1:02 a.m.