Triple
T31658284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scooby-Doo! Mystery Incorporated |
E807920
|
entity |
| Predicate | hasMainTeamName |
P7598
|
FINISHED |
| Object | Mystery Incorporated |
—
|
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: Mystery Incorporated | Statement: [Scooby-Doo! Mystery Incorporated, hasMainTeamName, Mystery Incorporated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainTeamName Context triple: [Scooby-Doo! Mystery Incorporated, hasMainTeamName, Mystery Incorporated]
-
A.
hasCompanionTeamName
Indicates that an entity is associated with a companion team identified by the given team name.
-
B.
teamName
chosen
Indicates the relationship that assigns or associates a specific name with a particular team.
-
C.
namedForTeam
Indicates that one entity has been given its name in honor of, or derived from, a particular team.
-
D.
associatedTeamName
Indicates the name of the team that is linked or connected to a given entity.
-
E.
teamNameRefersTo
Indicates that a given team name designates or refers to a specific team entity.
- 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_69f348daf95c81908b4c985b7ddcd0b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a00383e868c819098fd17e25fcbdb04 |
completed | May 10, 2026, 7:48 a.m. |
| PD | Predicate disambiguation | batch_6a0037cc59688190b7b9da939a413db3 |
completed | May 10, 2026, 7:46 a.m. |
Created at: April 30, 2026, 10:56 p.m.