Triple
T4192088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spamalot |
E89058
|
entity |
| Predicate | featuresCharacter |
P626
|
FINISHED |
| Object | Sir Lancelot |
E38009
|
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: Sir Lancelot | Statement: [Spamalot, featuresCharacter, Sir Lancelot]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sir Lancelot Context triple: [Spamalot, featuresCharacter, Sir Lancelot]
-
A.
Sir Lancelot
chosen
Sir Lancelot is one of the most famous Knights of the Round Table in Arthurian legend, renowned for his unmatched prowess in battle and his tragic love affair with Queen Guinevere.
-
B.
Lancelot
Lancelot is the codename of Roxy Morton, a skilled Kingsman agent in the "Kingsman" film series.
-
C.
Sir Galahad
Sir Galahad is a legendary knight of Arthurian romance renowned for his purity and for achieving the Holy Grail.
-
D.
Sir Tristram
Sir Tristram is a legendary knight of the Round Table in Arthurian romance, renowned for his prowess in battle and his tragic love affair with Iseult.
-
E.
Lancelot Heath
Lancelot Heath is an individual notable enough to be recognized as a prominent bearer of the surname Heath.
- 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_69aed9569a4481908b6c1fcec2a11e21 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af034169f88190a8eb170ba6008b79 |
completed | March 9, 2026, 5:28 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5961f0de081908e2b6bee1725b97e |
completed | March 14, 2026, 5:08 p.m. |
Created at: March 9, 2026, 3:46 p.m.