Triple
T33591262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suite from 'Broken Embraces' |
E860428
|
entity |
| Predicate | presentationForm |
P192080
|
FINISHED |
| Object | concert suite |
—
|
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: concert suite | Statement: [Suite from 'Broken Embraces', presentationForm, concert suite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentationForm Context triple: [Suite from 'Broken Embraces', presentationForm, concert suite]
-
A.
presentation
Indicates that one entity formally shows, explains, or demonstrates something (such as information, ideas, or a product) to an audience or another entity.
-
B.
presentationContext
Indicates the situational setting or environment in which a presentation, display, or communication of something takes place.
-
C.
presentationTime
Indicates the time at which something (such as information, media, or content) is presented or made visible to an audience.
-
D.
presentationMoment
Indicates the specific time or occasion at which something is formally presented or delivered.
-
E.
presentationLevel
Indicates the degree or intensity with which something is presented, displayed, or made perceptible in a given context.
- F. None of above. chosen
Provenance (4 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_69f3497e70e48190951c94d072879bec |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69fcf36bb86c8190a0a0ccf47cb56e5c |
completed | May 7, 2026, 8:17 p.m. |
Created at: May 1, 2026, 1:40 a.m.