Triple
T38079440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lotus Sutra hall |
E950811
|
entity |
| Predicate | relativeImportanceInTemple |
P51530
|
FINISHED |
| Object | principal hall |
—
|
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: principal hall | Statement: [Lotus Sutra hall, relativeImportanceInTemple, principal hall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeImportanceInTemple Context triple: [Lotus Sutra hall, relativeImportanceInTemple, principal hall]
-
A.
positionInTemple
chosen
Indicates the specific location or role an entity occupies within a temple.
-
B.
orientationWithinTemple
Indicates the spatial alignment or directional positioning of something relative to the interior layout of a temple.
-
C.
associatedTemple
Indicates a relationship where one entity is linked or connected to a particular temple, typically as its relevant or related religious site.
-
D.
attributesTempleTo
Indicates that a particular temple is ascribed, assigned, or associated to a specific entity, such as a deity, person, group, or place.
-
E.
mainTemple
Indicates that one entity serves as the primary or central temple associated with another entity.
- 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_69f76f02a6c48190a94f3c0b3ee90cf2 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:21 p.m.