Triple
T28998956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Good Grief (Demo) |
E736248
|
entity |
| Predicate | isDemoOf |
P166278
|
FINISHED |
| Object | Good Grief |
—
|
NE NERFINISHED |
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: Good Grief | Statement: [Good Grief (Demo), isDemoOf, Good Grief]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDemoOf Context triple: [Good Grief (Demo), isDemoOf, Good Grief]
-
A.
demonstratedBy
Indicates that something is shown, proven, or made evident through the actions, behavior, or example of a particular entity.
-
B.
demonstratedOn
Indicates that an action, behavior, or property is shown, illustrated, or proven using a particular entity as the example or subject.
-
C.
demonstratesTo
Indicates that one entity actively shows, explains, or proves something to another entity.
-
D.
designedToDemonstrate
Indicates that something was intentionally created or arranged for the purpose of showing, illustrating, or proving a particular concept, feature, or behavior.
-
E.
demonstratorType
Indicates the specific role or category of a demonstrator involved in an event, action, or demonstration.
- 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f66003a3f48190a2ba6da5aafbb5cb |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 28, 2026, 9:33 a.m.