Triple
T7629699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daeungjeon Hall |
E172727
|
entity |
| Predicate | functionInTempleLayout |
P51530
|
FINISHED |
| Object | spiritual and spatial center of Beomeosa Temple |
—
|
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: spiritual and spatial center of Beomeosa Temple | Statement: [Daeungjeon Hall, functionInTempleLayout, spiritual and spatial center of Beomeosa Temple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionInTempleLayout Context triple: [Daeungjeon Hall, functionInTempleLayout, spiritual and spatial center of Beomeosa Temple]
-
A.
positionInTemple
chosen
Indicates the specific location or role an entity occupies within a temple.
-
B.
mainTemple
Indicates that one entity serves as the primary or central temple associated with another entity.
-
C.
functionInText
Indicates that a text segment serves a specific rhetorical or structural function within a larger text.
-
D.
functionInRitual
Indicates that an entity serves a specific role or performs a particular function within a ritual.
-
E.
functionInWork
Indicates that a particular function, role, or operation is performed, utilized, or occurs within the context of a specific work or creation.
- 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_69c699517e348190bd3348b6889200f2 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6fe73ff7c8190ab1218d97b37416d |
completed | March 27, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e725a88190b1f05dd224f7f4f2 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:56 p.m.