Triple
T11856976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Myōshin-ji school |
E282063
|
entity |
| Predicate | followsLineage |
P82095
|
FINISHED |
| Object | Rinzai Zen lineage |
—
|
LITERAL 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: Rinzai Zen lineage | Statement: [Myōshin-ji school, followsLineage, Rinzai Zen lineage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsLineage Context triple: [Myōshin-ji school, followsLineage, Rinzai Zen lineage]
-
A.
followsGenerationsOf
Indicates that one entity comes after and is separated from another by multiple generations in a lineage or succession.
-
B.
isLineageType
chosen
Indicates that one entity represents a type or category within the lineage or ancestral line of another entity.
-
C.
successorInLineage
Indicates that one entity is the next direct descendant or inheritor in a genealogical or hierarchical lineage from another entity.
-
D.
hasLineageRole
Indicates a relationship where an entity holds a specific role or function within a lineage, ancestry, or genealogical chain.
-
E.
hasLineageDocumentedIn
Indicates that the lineage or ancestry of an entity is recorded or evidenced in a specified document or source.
- 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a699089c8190b7a298baf13dcded |
completed | April 10, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69d8a2573dbc8190ab432e8e28fde6cc |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.