Triple
T30625157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tendai |
E779555
|
entity |
| Predicate | majorTempleComplex |
P166281
|
FINISHED |
| Object | Enryaku-ji |
—
|
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: Enryaku-ji | Statement: [Tendai, majorTempleComplex, Enryaku-ji]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorTempleComplex Context triple: [Tendai, majorTempleComplex, Enryaku-ji]
-
A.
templeComplexFeature
chosen
Indicates that one entity is a structural or functional feature that forms part of a larger temple complex.
-
B.
majorTempleLocation
Indicates that a major temple associated with an entity is located at a specified place.
-
C.
templeComplexAreaInAcres
Indicates the total land area of a temple complex measured in acres.
-
D.
templeComplexLevel
Indicates the hierarchical level or rank of a temple within a larger temple complex or religious site structure.
-
E.
architecturalComplex
Indicates a relationship where multiple architectural structures or elements are grouped and function together as a single, integrated complex.
- 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_69f224a431548190a44ad9d088dbf91f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe5c1a502081909d4024e514309c8e |
completed | May 8, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69fe5a9df21c819087153f5d0bcaa987 |
completed | May 8, 2026, 9:50 p.m. |
Created at: April 29, 2026, 8:27 p.m.