Triple
T13937172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ector |
E335148
|
entity |
| Predicate | parentOf |
P120
|
FINISHED |
| Object | Sir Kay |
E211842
|
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 Kay | Statement: [Ector, parentOf, Sir Kay]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sir Kay Context triple: [Ector, parentOf, Sir Kay]
-
A.
Sir Kay
chosen
Sir Kay is a knight of Arthurian legend, traditionally depicted as King Arthur’s foster brother and seneschal, often characterized by his brash and sometimes boorish demeanor.
-
B.
Sir Gaheris
Sir Gaheris is a knight of the Round Table in Arthurian legend, a member of the Orkney clan and brother to Gawain, Gareth, and Agravain.
-
C.
Sir Geraint
Sir Geraint is a knight of Arthurian legend, best known from medieval Welsh and English romances for his chivalric exploits and his marriage to Enid.
-
D.
Sir Galahad
Sir Galahad is a legendary knight of Arthurian romance renowned for his purity and for achieving the Holy Grail.
-
E.
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.
- 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_69d81c5f739081908bc05b2461f54828 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2cf42878819085146670d7b92605 |
completed | April 14, 2026, 12:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7ce880a98819086ae25d3408bc723 |
completed | May 3, 2026, 10:39 p.m. |
Created at: April 9, 2026, 10:17 p.m.