Triple
T15097342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XIV Panzer Corps |
E360571
|
entity |
| Predicate | logisticalNeeds |
P28516
|
FINISHED |
| Object | high fuel consumption |
—
|
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: high fuel consumption | Statement: [XIV Panzer Corps, logisticalNeeds, high fuel consumption]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: logisticalNeeds Context triple: [XIV Panzer Corps, logisticalNeeds, high fuel consumption]
-
A.
logisticsSupportFrom
Indicates that one entity provides logistical assistance, resources, or services to another entity.
-
B.
logisticalEffect
Indicates the impact that one event, action, or condition has on the planning, coordination, or execution of logistical operations.
-
C.
logisticalCharacteristic
chosen
Indicates the logistical properties or constraints associated with an entity, such as how it is stored, transported, handled, or supplied.
-
D.
logistics
Indicates the organization, coordination, and management of how resources, goods, or information are efficiently moved and handled between entities.
-
E.
logisticsFeature
Indicates that something possesses a characteristic, capability, or function specifically related to logistics operations or processes.
- 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_69d85a035aa88190b52a139d3a1b7b6d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005466e9c8190a68e1fbeb8922b1a |
completed | April 15, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69deb9645b9c8190a5712456dbd78029 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:04 a.m.