Triple
T5649513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of Pater Noster |
E124466
|
entity |
| Predicate | hasCourtyardDecoration |
P62855
|
FINISHED |
| Object | wall-mounted prayer tablets |
—
|
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: wall-mounted prayer tablets | Statement: [Church of Pater Noster, hasCourtyardDecoration, wall-mounted prayer tablets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCourtyardDecoration Context triple: [Church of Pater Noster, hasCourtyardDecoration, wall-mounted prayer tablets]
-
A.
hasCourtyard
Indicates that one entity includes, features, or is characterized by the presence of a courtyard.
-
B.
hasCourtyardFeature
chosen
Indicates that a courtyard possesses or includes a specific feature or characteristic.
-
C.
hasCourtyardArea
Indicates that an entity includes or is associated with a courtyard and specifies the size or extent of that courtyard space.
-
D.
courtyardType
Indicates the specific kind or classification of a courtyard associated with an entity.
-
E.
hasCeilingDecoration
Indicates that an entity features or is adorned with a decorative element on its ceiling.
- 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_69c00825df388190a58742fa9b1aa33d |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022d2ed648190a5152c8668cbda02 |
completed | March 22, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69c01b2168508190b64b355cf50034ad |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:42 p.m.