Triple
T96454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finnish Army |
E1941
|
entity |
| Predicate | speciality |
P466
|
FINISHED |
| Object | winter warfare |
—
|
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: winter warfare | Statement: [Finnish Army, speciality, winter warfare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speciality Context triple: [Finnish Army, speciality, winter warfare]
-
A.
hasSpecialty
chosen
Indicates that an entity possesses a particular area of expertise, focus, or professional specialization.
-
B.
subjectMatter
Indicates the topic, theme, or content area that something (such as a work, document, or discussion) is about.
-
C.
category
Indicates that one entity is classified as a member or type within the grouping or class defined by another entity.
-
D.
sector
Indicates that an entity operates in, belongs to, or is associated with a particular economic or industrial sector.
-
E.
hasSpecialUnit
Indicates that an entity possesses or is associated with a distinct, designated unit that has a special role, function, or status.
- 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_69a24d4862f881908cc8b89d3a78031d |
completed | Feb. 28, 2026, 2:04 a.m. |
| NER | Named-entity recognition | batch_69a250cb400c8190b56343bbe19b48c7 |
completed | Feb. 28, 2026, 2:19 a.m. |
| PD | Predicate disambiguation | batch_69a24ebd19c48190bab291fea0ecc0c2 |
completed | Feb. 28, 2026, 2:11 a.m. |
Created at: Feb. 28, 2026, 2:09 a.m.