Triple
T7907618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Jurisdiction, Scottish Rite |
E183614
|
entity |
| Predicate | houseOfTheTempleFunction |
P79712
|
FINISHED |
| Object | headquarters and 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: headquarters and temple | Statement: [Southern Jurisdiction, Scottish Rite, houseOfTheTempleFunction, headquarters and temple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: houseOfTheTempleFunction Context triple: [Southern Jurisdiction, Scottish Rite, houseOfTheTempleFunction, headquarters and temple]
-
A.
mainTemple
Indicates that one entity serves as the primary or central temple associated with another entity.
-
B.
hasTempleOf
Indicates that a location or entity possesses, contains, or is the site of a temple dedicated to a particular deity, figure, or purpose.
-
C.
positionInTemple
Indicates the specific location or role an entity occupies within a temple.
-
D.
elementRepresentedByMainTemple
Indicates that a particular element is symbolized or embodied by the main temple in a given religious or cultural context.
-
E.
hasStepsToTemple
Indicates that one place or structure includes or provides a set of steps leading to a temple.
- F. None of above. chosen
Provenance (4 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_69ca828dec0c81908b8f55a4dbbb53ff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a59de00819099f1ce02bb469e75 |
completed | March 31, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69cae92f9498819085277879e59aa072 |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf7882b048190baa333af9f698590 |
completed | March 30, 2026, 10:22 p.m. |
Created at: March 30, 2026, 5:03 p.m.