Triple
T12153644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hatto (Dharma Hall) |
E289518
|
entity |
| Predicate | hasRoleWithinTemple |
P80423
|
FINISHED |
| Object | central public 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: central public hall | Statement: [Hatto (Dharma Hall), hasRoleWithinTemple, central public hall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoleWithinTemple Context triple: [Hatto (Dharma Hall), hasRoleWithinTemple, central public hall]
-
A.
roleAtTemple
chosen
Indicates that an entity holds or performs a specific role, function, or position at a particular temple.
-
B.
hasTempleDistrictRole
Indicates that an entity holds a specific role or function within a temple district.
-
C.
isActiveTemple
Indicates that a temple is currently functioning and in regular religious use, rather than being abandoned, ruined, or inactive.
-
D.
hasTempleOf
Indicates that a location or entity possesses, contains, or is the site of a temple dedicated to a particular deity, figure, or purpose.
-
E.
associatedWithTempleTown
Indicates a relationship where an entity has a connection or linkage to a town that is characterized by or centered around a temple.
- 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_69d6ab4c6710819097a9d228382dde43 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d915d7109481908bf5fe512bba3c89 |
completed | April 10, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69d9150c18148190bf8152189c0e5fca |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:50 p.m.