Triple
T33754054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wespe |
E864923
|
entity |
| Predicate | baseVehicle |
P154160
|
FINISHED |
| Object | Panzer II Ausf. F (modified chassis) |
—
|
NE NERFINISHED |
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: Panzer II Ausf. F (modified chassis) | Statement: [Wespe, baseVehicle, Panzer II Ausf. F (modified chassis)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: baseVehicle Context triple: [Wespe, baseVehicle, Panzer II Ausf. F (modified chassis)]
-
A.
vehicleBase
chosen
Indicates that one entity serves as the foundational or underlying base for a vehicle-related entity or system.
-
B.
mainVehicle
Indicates that one vehicle is the primary or most important vehicle associated with a given entity or context.
-
C.
hostVehicle
Indicates that one entity serves as the primary or reference vehicle in relation to another entity or context.
-
D.
controlVehicle
Indicates having the authority or ability to direct, operate, or manage the movement and functioning of a vehicle.
-
E.
parentVehicle
Indicates that one vehicle serves as the primary or containing vehicle from which another vehicle is derived, owned, or hierarchically related.
- 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_69f3498c35f881909df279ae4270f831 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb91fed4819087217c53d6fecf28 |
completed | May 3, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69f6f96ea0c08190902a3d0e1f263e8c |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:45 a.m.