Triple
T2219395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Rêve – The Dream |
E48104
|
entity |
| Predicate | performanceRun |
P6103
|
FINISHED |
| Object | 2005–2020 |
—
|
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: 2005–2020 | Statement: [Le Rêve – The Dream, performanceRun, 2005–2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performanceRun Context triple: [Le Rêve – The Dream, performanceRun, 2005–2020]
-
A.
performance
Indicates that one entity’s effectiveness, quality, or success in carrying out a task, function, or role is being evaluated or characterized in relation to some standard or expectation.
-
B.
featuresPerformanceBy
chosen
Indicates a relationship where something (such as an event, work, or production) includes or showcases a performance given by a particular performer or group.
-
C.
runsFrom
Indicates that one entity flees or escapes away from another entity.
-
D.
runsDirection
Indicates that an entity moves or operates in a specified direction.
-
E.
impactOnPerformance
Indicates that one entity has an effect, influence, or consequence on the performance level or effectiveness of another entity.
- 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.