Triple
T30836173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pirates Dinner Adventure |
E785368
|
entity |
| Predicate | entertainmentFormat |
P30079
|
FINISHED |
| Object | dinner and show |
—
|
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: dinner and show | Statement: [Pirates Dinner Adventure, entertainmentFormat, dinner and show]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entertainmentFormat Context triple: [Pirates Dinner Adventure, entertainmentFormat, dinner and show]
-
A.
entertainmentType
chosen
Indicates the kind or category of entertainment associated with an entity or event.
-
B.
entertainmentFocus
Indicates that one entity is primarily concerned with, directed toward, or centered on providing or engaging in entertainment for another entity or context.
-
C.
portrayalFormat
Indicates the medium or format in which something is portrayed or represented (e.g., painting, sculpture, film, digital).
-
D.
filmContent
Indicates that one entity is the substantive material or subject matter contained within a film.
-
E.
isScriptedEntertainment
Indicates that the entertainment content is pre-planned and follows a written script rather than being spontaneous or unscripted.
- 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_69f224b73d8c81908129383bfb397c87 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 29, 2026, 8:45 p.m.