Triple
T2219310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romantic nationalism |
E48103
|
entity |
| Predicate | hasPeriodOfProminence |
P24496
|
FINISHED |
| Object | 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: 19th century | Statement: [Romantic nationalism, hasPeriodOfProminence, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPeriodOfProminence Context triple: [Romantic nationalism, hasPeriodOfProminence, 19th century]
-
A.
hasProminence
Indicates that one entity stands out in importance, visibility, or influence relative to others within a given context.
-
B.
timePeriodOfDominance
Indicates the span of time during which an entity held dominance, control, or prevailing influence over another entity or context.
-
C.
hasMainPeriod
Indicates that something is associated with or characterized by a primary or most significant time period.
-
D.
wasProminentIn
chosen
Indicates that an entity was notably active, influential, or widely recognized within a particular field, context, or time period.
-
E.
hasProminentAspect
Indicates that an entity possesses a particularly notable, dominant, or emphasized aspect or feature.
- 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_69a88aa1ee708190862c8c378c41e9eb |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc011d50c8190b1c375cc633f8189 |
completed | March 7, 2026, 6:05 a.m. |
| PD | Predicate disambiguation | batch_69abbdac31d8819092d17815e11921e9 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.