Triple
T28332112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roma Symphony |
E717562
|
entity |
| Predicate | reflectsStylePeriod |
P18647
|
FINISHED |
| Object | early symphonic style of Georges Bizet |
—
|
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: early symphonic style of Georges Bizet | Statement: [Roma Symphony, reflectsStylePeriod, early symphonic style of Georges Bizet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reflectsStylePeriod Context triple: [Roma Symphony, reflectsStylePeriod, early symphonic style of Georges Bizet]
-
A.
stylePeriod
chosen
Indicates the stylistic or historical period with which an entity (such as an artwork, artifact, or performance) is associated.
-
B.
timePeriodReflected
Indicates that one entity represents or corresponds to the time period associated with another entity.
-
C.
refersToPeriod
Indicates that one entity designates, references, or is associated with a specific time period or interval.
-
D.
periodizedAs
Indicates that something has been divided or organized into distinct time periods according to a particular periodization scheme.
-
E.
periodProperty
Indicates a temporal characteristic or attribute associated with a specific time period or interval.
- 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_69eff6e9a57c8190a69c2c74b5d72119 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 12:33 a.m.