Triple
T6167056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cardston Alberta Temple |
E137592
|
entity |
| Predicate | hasOrdinanceRoom |
P69170
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Cardston Alberta Temple, hasOrdinanceRoom, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrdinanceRoom Context triple: [Cardston Alberta Temple, hasOrdinanceRoom, yes]
-
A.
hasPlenaryChamber
Indicates that an institution or governing body possesses a designated plenary chamber where all members can meet and deliberate together.
-
B.
recognizedAsOrdinanceBy
Indicates that something is formally acknowledged or accepted as an ordinance by a particular authority or governing body.
-
C.
hasChambersFor
Indicates that one entity contains or provides designated chambers or compartments intended for use by another entity.
-
D.
isLargerChamberOf
Indicates that one chamber or room has a greater size or capacity than another chamber.
-
E.
hasHigherChamber
Indicates that one legislative or decision-making body functions as the upper or more senior chamber relative to another within the same institutional structure.
- 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_69c008a68c508190a8d78245c865960e |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d6366948190b35ef44dd9d6fcd6 |
completed | March 22, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69c055f5b81481908819515cdc334ae6 |
completed | March 22, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69c056df95ac8190bc5efe050d3af864 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:17 p.m.