Triple
T27687189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porsche Tiger |
E698062
|
entity |
| Predicate | fateOfChassis |
P162948
|
FINISHED |
| Object | converted to Ferdinand tank destroyers |
—
|
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: converted to Ferdinand tank destroyers | Statement: [Porsche Tiger, fateOfChassis, converted to Ferdinand tank destroyers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fateOfChassis Context triple: [Porsche Tiger, fateOfChassis, converted to Ferdinand tank destroyers]
-
A.
chassis
Indicates that one entity serves as the structural frame or supporting base (chassis) for another entity.
-
B.
usedChassisFor
Indicates that one entity employed or incorporated another entity’s chassis as the structural base or framework for its construction or operation.
-
C.
chassisConstruction
Indicates how the chassis of an object is built or assembled, specifying the construction method or structural design used.
-
D.
chassisOrigin
Indicates the place or source from which a chassis was originally produced, manufactured, or derived.
-
E.
chassisFeature
Indicates that a particular feature, component, or characteristic is part of or associated with a chassis.
- F. None of above. chosen
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_69ef590df8708190af5488f0638e790c |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f63574d2388190839cd1061e3c9074 |
completed | May 2, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f6305219f08190b55f6193a4a49984 |
completed | May 2, 2026, 5:11 p.m. |
Created at: April 27, 2026, 2:50 p.m.