Triple
T15434844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of Panagia Evangelistria |
E369731
|
entity |
| Predicate | hasCourtyardUse |
P118767
|
FINISHED |
| Object | gathering place for large pilgrim crowds |
—
|
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: gathering place for large pilgrim crowds | Statement: [Church of Panagia Evangelistria, hasCourtyardUse, gathering place for large pilgrim crowds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCourtyardUse Context triple: [Church of Panagia Evangelistria, hasCourtyardUse, gathering place for large pilgrim crowds]
-
A.
hasCourtyard
Indicates that one entity includes, features, or is characterized by the presence of a courtyard.
-
B.
hasCourtyardFeature
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.
hasPorchUse
Indicates that something includes or permits the use of a porch as part of its function, design, or occupancy.
-
E.
courtyardType
Indicates the specific kind or classification of a courtyard associated with an entity.
- 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_69d85a19180081909925012fbf4e62a3 |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03edb3ec481908b26164d4470c9bc |
completed | April 16, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69ded27f45548190a6d2b1b85cb47444 |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57005608190886cd01f640dfedb |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:21 a.m.