Triple
T38069689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morg |
E950560
|
entity |
| Predicate | successorAsHerald |
P202916
|
FINISHED |
| Object | Silver Surfer |
—
|
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: Silver Surfer | Statement: [Morg, successorAsHerald, Silver Surfer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorAsHerald Context triple: [Morg, successorAsHerald, Silver Surfer]
-
A.
predecessorAsHerald
Indicates that one entity served as a herald or forerunner for another entity that later succeeded it.
-
B.
ceremonialSuccessor
Indicates that one entity formally follows another in a role or position in a purely symbolic or ceremonial capacity, without inheriting its actual powers or responsibilities.
-
C.
servedAsHeraldOf
Indicates that one entity acted as a herald for another, formally announcing, representing, or proclaiming that entity or its arrival.
-
D.
successorAsLordOf
Indicates that one entity takes over the role or title of lord from another entity, becoming their direct successor in that lordship.
-
E.
successorMonogram
Indicates that one monogram directly follows or replaces another in a sequence or lineage.
- F. None of above. chosen
Provenance (4 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_69f76f02a6c48190a94f3c0b3ee90cf2 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a00cda99c908190980e0bf54cb2e2a4 |
completed | May 10, 2026, 6:25 p.m. |
| PD | Predicate disambiguation | batch_6a00cd1635b08190a791ecfcf87a1d54 |
completed | May 10, 2026, 6:23 p.m. |
| PDg | Predicate description generation | batch_6a00cda8ed348190950ee34bb24ae65b |
completed | May 10, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:21 p.m.