Triple
T36152938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scooby-Doo monsters gallery |
E1045641
|
entity |
| Predicate | includesEntriesFrom |
P1393
|
FINISHED |
| Object | Scooby-Doo, Where Are You! |
E922996
|
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: Scooby-Doo, Where Are You! | Statement: [Scooby-Doo monsters gallery, includesEntriesFrom, Scooby-Doo, Where Are You!]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesEntriesFrom Context triple: [Scooby-Doo monsters gallery, includesEntriesFrom, Scooby-Doo, Where Are You!]
-
A.
includedWith
Indicates that one entity is provided or packaged together as part of another entity.
-
B.
includesDataFrom
Indicates that one entity’s data set contains or incorporates data originating from another entity.
-
C.
includesMap
Indicates that one entity contains or incorporates another entity in the form of a map or mapping structure.
-
D.
includes
chosen
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
E.
includesModelsFrom
Indicates that one collection, set, or group contains models that originate from or are derived from another source or collection.
- 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_69f76e38903c8190a52887620f90aabe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a390d4e48d481909cbc0f208dea1e05 |
completed | June 22, 2026, 10:24 a.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:08 p.m.