Triple
T25158540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corum series |
E626378
|
entity |
| Predicate | hasHeroTitle |
P162864
|
FINISHED |
| Object | Prince in the Scarlet Robe |
E1665680
|
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: Prince in the Scarlet Robe | Statement: [Corum series, hasHeroTitle, Prince in the Scarlet Robe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeroTitle Context triple: [Corum series, hasHeroTitle, Prince in the Scarlet Robe]
-
A.
hasTitleOver
Indicates that one entity holds a formal title, rank, or designation in relation to another entity.
-
B.
hasTitleCard
Indicates that an entity is associated with a title card, such as an introductory or identifying screen or graphic.
-
C.
hasTitleFeature
Indicates that an entity possesses a specific characteristic, attribute, or element related to its title.
-
D.
hasTitleOf
Indicates that one entity holds, bears, or is designated by the official title, name, or rank specified by another entity.
-
E.
hasMainTitleCharacter
Indicates that a work’s primary or main title is centered on, derived from, or explicitly names a particular character.
- F. None of above. chosen
Provenance (5 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_69e2ff2834ec8190b0872e2ec3d76023 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f62e83045c8190a424a2e401a88e9e |
completed | May 2, 2026, 5:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a1067c45a2c8190a1d265a67f5e574a |
completed | May 22, 2026, 2:27 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f62d886828819080ec2f742b9449e3 |
completed | May 2, 2026, 4:59 p.m. |
Created at: April 18, 2026, 6:31 a.m.