Triple
T37937041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sakya |
E946376
|
entity |
| Predicate | patronPriestRelationshipWith |
P165270
|
FINISHED |
| Object | Kublai Khan |
—
|
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: Kublai Khan | Statement: [Sakya, patronPriestRelationshipWith, Kublai Khan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patronPriestRelationshipWith Context triple: [Sakya, patronPriestRelationshipWith, Kublai Khan]
-
A.
hasLiturgicalRelationTo
Indicates a relationship in which one entity is connected to another through liturgical roles, functions, practices, or contexts within religious worship.
-
B.
priests
Indicates that the subject serves in a religious or spiritual officiating role, typically performing sacred rituals or duties for a faith community.
-
C.
patron of
chosen
Indicates a supportive relationship in which one entity provides sponsorship, protection, or backing to another, often enabling its activities or development.
-
D.
relationshipToMonk
Indicates the specific type of relationship an entity has to a monk, such as familial, social, or institutional connection.
-
E.
religiousPatronageIn
Indicates that an entity provides religious patronage, support, or sponsorship within a specified place or region.
- F. None of above.
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_69f76ef531ac8190ae6d99e5786e76ec |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.