Triple
T2601011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maitreya |
E58341
|
entity |
| Predicate | hasTempleDedicated |
P28305
|
FINISHED |
| Object | Maitreya temples and halls in East Asia |
—
|
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: Maitreya temples and halls in East Asia | Statement: [Maitreya, hasTempleDedicated, Maitreya temples and halls in East Asia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTempleDedicated Context triple: [Maitreya, hasTempleDedicated, Maitreya temples and halls in East Asia]
-
A.
hadTempleDedicatedTo
chosen
Indicates that a temple was formally dedicated in honor of, or for the worship of, a particular entity.
-
B.
hasTemplePurpose
Indicates that something (such as a building, site, or structure) is intended, used, or designated for temple-related purposes or functions.
-
C.
lastMajorTempleClosed
Indicates the time or event at which the final significant temple associated with an entity was permanently closed.
-
D.
hasMajorShrine
Indicates that one entity serves as a principal or primary shrine dedicated to another entity.
-
E.
templeOpening
Indicates that a temple begins operating or becomes accessible for worship, visitation, or related activities.
- 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_69ab4ac14040819098b13f4a27d5c8ff |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd4587014819089f78e93adf2144c |
completed | March 7, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69abd0d4e8648190b612eb09aa085451 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.