Triple
T38418801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ram artillery tractor |
E903171
|
entity |
| Predicate | primaryTheatreOfUse |
P5783
|
FINISHED |
| Object | Northwest Europe campaign |
E230525
|
NE 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: Northwest Europe campaign | Statement: [Ram artillery tractor, primaryTheatreOfUse, Northwest Europe campaign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryTheatreOfUse Context triple: [Ram artillery tractor, primaryTheatreOfUse, Northwest Europe campaign]
-
A.
primaryUseOf
Indicates that one entity serves as the main or principal function, purpose, or application of another entity.
-
B.
regionPrimaryUse
Indicates the main functional purpose or dominant activity for which a region is used.
-
C.
eraOfPrimaryMilitaryUse
Indicates the historical time period during which the subject was primarily used for military purposes.
-
D.
primaryTheater
chosen
Indicates that a particular location or region is the main setting or principal area where an event, activity, or operation takes place.
-
E.
isPrimarilyUsedAs
Indicates that one entity serves mainly or most commonly in the role, function, or purpose specified by the other entity.
- F. None of above.
Provenance (4 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_69f76e67e4fc8190a7d08dfe9a8af998 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41cca1b7fc8190bceb47d1926f2caf |
completed | June 29, 2026, 1:38 a.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.