Triple
T2439451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | StuG III |
E53237
|
entity |
| Predicate | hasSuperstructure |
P8273
|
FINISHED |
| Object | fixed casemate |
—
|
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: fixed casemate | Statement: [StuG III, hasSuperstructure, fixed casemate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuperstructure Context triple: [StuG III, hasSuperstructure, fixed casemate]
-
A.
hasIslandSuperstructure
Indicates that one entity possesses or includes an island-like elevated central structure as a distinct component or feature.
-
B.
hasSuperstrate
Indicates that one material, layer, or structure lies above and is supported by another in a layered or composite arrangement.
-
C.
hasStructureAbove
chosen
Indicates that one entity has another entity positioned vertically higher or located on top of it within a structural or spatial arrangement.
-
D.
surpassedStructure
Indicates that one entity has exceeded or gone beyond another entity in terms of structural capacity, performance, or advancement.
-
E.
hasUpperFloor
Indicates that one entity possesses or includes an upper floor relative to another level or reference point.
- 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_69ab495b6dac8190ac82661aa1452222 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcebf7cac8190889e6890d72c256c |
completed | March 7, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69abc5ac11b081908ce6a506e81a742a |
completed | March 7, 2026, 6:29 a.m. |
Created at: March 6, 2026, 9:43 p.m.