Triple
T11644637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The New Middle Ages |
E276748
|
entity |
| Predicate | viewsModernityAs |
P25075
|
FINISHED |
| Object | spiritually exhausted |
—
|
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: spiritually exhausted | Statement: [The New Middle Ages, viewsModernityAs, spiritually exhausted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewsModernityAs Context triple: [The New Middle Ages, viewsModernityAs, spiritually exhausted]
-
A.
hasViewOnModernity
chosen
Indicates that an entity holds a particular perspective, stance, or interpretation regarding modernity.
-
B.
formedModern
Indicates that an entity created, established, or organized another entity in the modern era or in its current modern form.
-
C.
nearModernSite
Indicates that one entity is located in close physical proximity to a site or location from the modern era.
-
D.
isModern
Indicates that something belongs to, reflects, or is characteristic of the contemporary or recent period, especially in style, design, or thinking.
-
E.
modernization
Indicates a process by which something is updated, reformed, or transformed to align with contemporary standards, technologies, or practices.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a2cb4ca88190a9322f08416d3974 |
completed | April 10, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69d85dd94bdc819091fa2ed33eb31624 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.