Triple
T38079547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiantai patriarchs |
E950813
|
entity |
| Predicate | mostFamousPatriarch |
P40163
|
FINISHED |
| Object | Zhiyi |
—
|
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: Zhiyi | Statement: [Tiantai patriarchs, mostFamousPatriarch, Zhiyi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mostFamousPatriarch Context triple: [Tiantai patriarchs, mostFamousPatriarch, Zhiyi]
-
A.
fatherNotableFor
Indicates that a person's father is recognized or distinguished for a particular achievement, role, or characteristic.
-
B.
patriarchFeatured
Indicates that a patriarch is prominently highlighted or given special emphasis in relation to something (such as a work, event, or context).
-
C.
fatherNotableAs
Indicates that someone is recognized or distinguished specifically in their role as a father.
-
D.
mostFamousBearer
chosen
Indicates that one entity is the most widely recognized or renowned individual associated with a particular name, title, or attribute compared to all other bearers of it.
-
E.
patriarch
Indicates a relationship where one entity serves as the male head or senior father-figure authority over a family, clan, or lineage of other entities.
- 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_69f76f02a6c48190a94f3c0b3ee90cf2 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.