Triple
T20892695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Degeneration |
E514446
|
entity |
| Predicate | positionOnModernism |
P25075
|
FINISHED |
| Object | hostile |
—
|
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: hostile | Statement: [Degeneration, positionOnModernism, hostile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnModernism Context triple: [Degeneration, positionOnModernism, hostile]
-
A.
hasViewOnModernity
chosen
Indicates that an entity holds a particular perspective, stance, or interpretation regarding modernity.
-
B.
modernInfluence
Indicates that one entity has a shaping or impactful effect on another within a contemporary or current context.
-
C.
formedModern
Indicates that an entity created, established, or organized another entity in the modern era or in its current modern form.
-
D.
isModernistCity
Indicates that a city embodies characteristics of modernist urban design, architecture, and planning principles.
-
E.
associatedWithModernization
Indicates a relationship in which an entity is connected to, involved in, or influenced by processes, policies, or efforts of modernization.
- 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_69e0b4f7ebe48190952a85547a0f31a1 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6d05f0bec8190a296db546bd34114 |
completed | April 21, 2026, 1:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a8dc148190b33ff51894e2a8f9 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:46 p.m.