Triple
T30097815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keu |
E764912
|
entity |
| Predicate | relativeInTradition |
P203788
|
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: [Keu, relativeInTradition, Sir Kay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeInTradition Context triple: [Keu, relativeInTradition, Sir Kay]
-
A.
linkedToTradition
Indicates a relationship where something is connected or related to a particular tradition, heritage, or customary practice.
-
B.
usesTradition
Indicates that one entity employs or draws upon a tradition as a guiding method, resource, or influence in its actions or practices.
-
C.
mainTradition
Indicates that one entity represents the primary or dominant tradition associated with another entity.
-
D.
foundedInTradition
Indicates that something is established, developed, or grounded within a particular tradition or set of longstanding customary practices.
-
E.
governedWithinTradition
Indicates that an entity’s actions, decisions, or organization are regulated or constrained according to a particular established tradition or customary framework.
- 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_69f22474e4288190b5f895fe3974aa92 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0204dafcc08190868a6f3eab162505 |
completed | May 11, 2026, 4:33 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a276eddd0548190aa148f088243481e |
completed | June 9, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_6a0202dc60348190a140bb9da906f5b6 |
completed | May 11, 2026, 4:25 p.m. |
| PDg | Predicate description generation | batch_6a0204da26f4819087ff47e984810a6f |
completed | May 11, 2026, 4:33 p.m. |
Created at: April 29, 2026, 7:07 p.m.