Triple
T35881268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mystery Inc. |
E1037512
|
entity |
| Predicate | baitCharacter |
P87321
|
FINISHED |
| Object | Shaggy Rogers |
—
|
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: Shaggy Rogers | Statement: [Mystery Inc., baitCharacter, Shaggy Rogers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: baitCharacter Context triple: [Mystery Inc., baitCharacter, Shaggy Rogers]
-
A.
bossCharacter
Indicates that one character serves as the primary, often more powerful, opponent or leader that others must confront or overcome.
-
B.
enemyCharacterIn
Indicates that a character is located within or present inside an enemy-controlled area, zone, or context.
-
C.
targetsCharacter
chosen
Indicates that one entity is the intended focus or target of another entity’s action, effect, or behavior.
-
D.
petCharacter
Indicates that one entity is a pet belonging to, cared for by, or closely associated with another entity as its owner or companion.
-
E.
hatCharakter
Indicates that an entity possesses or exhibits a particular character, trait, or quality.
- 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_69f76e1f4d748190bb55594d8441d70e |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa3883d48190b05e3d2da7a017ae |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.