Triple
T37225582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scooby-Doo, Where Are You! |
E922996
|
entity |
| Predicate | hasProtagonistGroupName |
P24067
|
FINISHED |
| Object | Mystery Inc. |
E1037512
|
NE 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: Mystery Inc. | Statement: [Scooby-Doo, Where Are You!, hasProtagonistGroupName, Mystery Inc.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProtagonistGroupName Context triple: [Scooby-Doo, Where Are You!, hasProtagonistGroupName, Mystery Inc.]
-
A.
hasProtagonistGroup
chosen
Indicates that a narrative work features a central group of characters who collectively serve as the main protagonists.
-
B.
hasProtagonist
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
-
C.
hasProtagonistClass
Indicates that a work’s main character belongs to a specified class or category.
-
D.
hasFriendGroupName
Indicates that an entity is associated with a friend group identified by a specific name.
-
E.
hasCharacterGroupName
Indicates that an entity is associated with a specific name identifying a group of characters.
- F. None of above.
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_69f76ea7f0008190b31b8e30f3d05a71 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4043bcbe548190bccc04bcdd408aaf |
completed | June 27, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:15 p.m.