Triple
T16728772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 天台宗 |
E406530
|
entity |
| Predicate | 教義的特徴 |
P33315
|
FINISHED |
| Object | 法華一乗思想 |
—
|
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: 法華一乗思想 | Statement: [天台宗, 教義的特徴, 法華一乗思想]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 教義的特徴 Context triple: [天台宗, 教義的特徴, 法華一乗思想]
-
A.
hasDoctrinalCharacteristic
chosen
Indicates that an entity possesses a specific doctrinal feature, quality, or attribute within a belief or teaching system.
-
B.
religiousCharacteristic
Indicates that one entity has a religious attribute, quality, or affiliation that characterizes or distinguishes it in a religious context.
-
C.
doctrinalTheme
Indicates that one entity concerns, expresses, or is characterized by a particular doctrinal or theological theme in relation to another.
-
D.
doctrinalEmphasis
Indicates a relationship where a doctrine, belief system, or teaching is given particular focus, priority, or stress within a religious, ideological, or organizational context.
-
E.
spiritualityCharacteristic
Indicates that one entity possesses, exhibits, or is defined by a spiritual quality, trait, or aspect in relation to another.
- 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e38749baa48190892b2e2b978f6eb6 |
completed | April 18, 2026, 1:29 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:20 a.m.