Triple
T33580233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Logan Utah Temple |
E860129
|
entity |
| Predicate | hasCastleLikeAppearance |
P199323
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Logan Utah Temple, hasCastleLikeAppearance, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCastleLikeAppearance Context triple: [Logan Utah Temple, hasCastleLikeAppearance, true]
-
A.
hasCastle
Indicates that one entity possesses, controls, or contains a castle.
-
B.
hasCastleFeature
Indicates that an entity possesses or includes a specific architectural or structural feature of a castle.
-
C.
hasCastleType
Indicates that an entity is associated with, characterized by, or classified as a specific type of castle.
-
D.
hasCastleRemains
Indicates that one entity possesses or contains the remaining structures or ruins of a castle associated with it.
-
E.
hasCastleUse
Indicates that something is used or designated for a particular castle-related purpose or function.
- 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_69f3497d37848190afcbb5ef3f5c7376 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff2eb19ad88190915fbbe08e8bc84e |
completed | May 9, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69ff2db5dd608190b7b7ba95f19c276c |
completed | May 9, 2026, 12:51 p.m. |
| PDg | Predicate description generation | batch_69ff2eb0c0888190b0e05a03bf06d388 |
completed | May 9, 2026, 12:55 p.m. |
Created at: May 1, 2026, 1:40 a.m.