Triple
T405588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian Renaissance Revival |
E9375
|
entity |
| Predicate | hasPeakPopularity |
P2927
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [Italian Renaissance Revival, hasPeakPopularity, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPeakPopularity Context triple: [Italian Renaissance Revival, hasPeakPopularity, late 19th century]
-
A.
hasPeak
Indicates that something possesses or contains a highest point, summit, or maximum value.
-
B.
peakPopularity
chosen
Indicates the time or context in which something reaches its highest level of popularity relative to other times or contexts.
-
C.
isPopularWith
Indicates that one entity is well-liked, favored, or widely accepted by another entity or group.
-
D.
popularInPeriod
Indicates that something is widely liked, used, or influential during a specified time period.
-
E.
hasProminence
Indicates that one entity stands out in importance, visibility, or influence relative to others within a given context.
- 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_69a2e8004cb88190b92ed1add6abf41a |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ecbc00508190bbb602179273f29c |
completed | Feb. 28, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69a2e97066e8819083cc1b3a421b9650 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.