Triple
T36957475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Die, Führer, Die! |
E914223
|
entity |
| Predicate | hasMapLayout |
P204263
|
FINISHED |
| Object | maze-like corridors |
—
|
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: maze-like corridors | Statement: [Die, Führer, Die!, hasMapLayout, maze-like corridors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMapLayout Context triple: [Die, Führer, Die!, hasMapLayout, maze-like corridors]
-
A.
hasMapframe
Indicates that an entity is associated with an embedded, interactive map frame representation of its geographic location or area.
-
B.
hasMapRegion
Indicates that an entity is associated with, or belongs to, a specific geographic or logical map region.
-
C.
hasMapType
Indicates that one entity is associated with a specific type or category of map.
-
D.
hasMapContent
Indicates that an entity includes or is associated with specific map-related data or content.
-
E.
hasMaps
Indicates that one entity possesses, includes, or provides access to one or more maps associated with another entity.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a035ac41d088190b7e76b93c1410090 |
completed | May 12, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_6a035a4f290c8190a0101295a38ae8b8 |
completed | May 12, 2026, 4:50 p.m. |
| PDg | Predicate description generation | batch_6a035ac33bb08190b338ad792ab1b6cd |
completed | May 12, 2026, 4:52 p.m. |
Created at: May 3, 2026, 4:13 p.m.