Triple
T26910158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dorothy Spinner |
E677361
|
entity |
| Predicate | comicBookTeam |
P79038
|
FINISHED |
| Object | Doom Patrol |
—
|
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: Doom Patrol | Statement: [Dorothy Spinner, comicBookTeam, Doom Patrol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: comicBookTeam Context triple: [Dorothy Spinner, comicBookTeam, Doom Patrol]
-
A.
fictionalTeam
chosen
Indicates that the related entities are members of, or otherwise associated with, the same fictional team within a narrative or imaginary context.
-
B.
mainSupermanBatmanTeamUpEndIssue
Indicates that the primary storyline in which Superman and Batman team up concludes in this specific comic issue.
-
C.
featuredTeam
Indicates that a particular team is highlighted or given special prominence in a given context or presentation.
-
D.
AllStarTeam
Indicates that an entity has been selected for inclusion on an all-star team, recognizing it as one of the top performers within a league, season, or competition.
-
E.
coreTeams
Indicates that the entities are part of the same primary or central team within an organization or project.
- 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_69eee9bcef1c8190be88586bb902bb9b |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61fd9d3208190aa7d3d12cb4db479 |
completed | May 2, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 6:01 a.m.