Triple
T31511392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Dominators |
E803950
|
entity |
| Predicate | introducesCharacterType |
P50197
|
FINISHED |
| Object | Quarks |
—
|
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: Quarks | Statement: [The Dominators, introducesCharacterType, Quarks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducesCharacterType Context triple: [The Dominators, introducesCharacterType, Quarks]
-
A.
introducesCharacterSpecies
chosen
Indicates that an entity presents or brings into a context the species to which a character belongs.
-
B.
introducesFictionalCharacter
Indicates that one entity is responsible for first presenting or bringing a fictional character into a narrative work or story.
-
C.
helpsCharacterType
Indicates that one character type provides assistance or support to another character type.
-
D.
introducesSeriesCharacters
Indicates that an entity is responsible for first presenting or bringing specific characters into a series.
-
E.
establishesCharacter
Indicates that one entity defines, introduces, or sets up the identity or traits of a character in relation to another entity or context.
- 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_69f348ceb0a48190ae7feca263b6296c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: April 30, 2026, 9:50 p.m.