Triple
T38079434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lotus Sutra hall |
E950811
|
entity |
| Predicate | centralScriptureEnshrined |
P196613
|
FINISHED |
| Object | Lotus Sutra |
—
|
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: Lotus Sutra | Statement: [Lotus Sutra hall, centralScriptureEnshrined, Lotus Sutra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralScriptureEnshrined Context triple: [Lotus Sutra hall, centralScriptureEnshrined, Lotus Sutra]
-
A.
canonizedScriptureIn
Indicates that a text or scripture has been formally recognized and included as canonical within a particular religious tradition, community, or collection.
-
B.
centralFigureVenerated
Indicates that the subject is regarded and honored as a primary or focal object of reverence or worship by others.
-
C.
centralActOfWorshipOf
Indicates that one entity serves as the primary or most important act of worship directed toward another entity.
-
D.
receivedScripture
Indicates that one entity has been given or accepted a body of sacred or authoritative religious writings from another source.
-
E.
primaryScriptureOfReligion
Indicates that a given text serves as the main or authoritative scripture for a particular religion.
- F. None of above. chosen
Provenance (4 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_69fe5d58c3e48190910aa3c23485e2c4 |
completed | May 8, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69fe5c92090c8190bcfa412c0a3619df |
completed | May 8, 2026, 9:58 p.m. |
| PDg | Predicate description generation | batch_69fe5d580d7c819097cb18d438b01d08 |
completed | May 8, 2026, 10:02 p.m. |
Created at: May 3, 2026, 4:21 p.m.