Triple
T21535919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tristram |
E531347
|
entity |
| Predicate | followsWork |
P9710
|
FINISHED |
| Object | Merlin |
E38868
|
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: Merlin | Statement: [Tristram, followsWork, Merlin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Merlin Context triple: [Tristram, followsWork, Merlin]
-
A.
Merlin
chosen
Merlin is the legendary wizard of Arthurian myth, often depicted as King Arthur’s powerful but enigmatic advisor and magician.
-
B.
Merlin
Merlin is a key supporting character in the "Kingsman" film series, serving as the tech expert and tactical coordinator for the Kingsman organization.
-
C.
Merlin
Merlin is a 1983 Broadway musical that reimagines the legendary wizard’s story through elaborate stage magic and dance.
-
D.
Merlin (TV series)
Merlin is a British fantasy-adventure television series that reimagines the Arthurian legends by following a young Merlin as he secretly uses magic to protect Prince Arthur in the kingdom of Camelot.
-
E.
Pendragon
Pendragon is the legendary surname and title associated with King Uther and his son King Arthur in Arthurian mythology, symbolizing their royal and dragon-linked lineage.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69e0c45e5b8881908ac18fc2f493b114 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee9d0ce8d08190b3233d7117a9b1ca |
completed | April 26, 2026, 11:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a09e8339c04819092968f7a7baba3f8 |
completed | May 17, 2026, 4:09 p.m. |
Created at: April 16, 2026, 6:27 p.m.