Triple
T38623250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St George’s Parish Church |
E936931
|
entity |
| Predicate | hasAltarCount |
P131059
|
FINISHED |
| Object | multiple side altars |
—
|
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: multiple side altars | Statement: [St George’s Parish Church, hasAltarCount, multiple side altars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAltarCount Context triple: [St George’s Parish Church, hasAltarCount, multiple side altars]
-
A.
hasAltar
Indicates that one entity possesses, contains, or includes an altar as part of its features or components.
-
B.
numberOfAltars
chosen
Indicates the quantity of altars associated with a given entity or context.
-
C.
hasAltarLocation
Indicates that an altar is situated at or associated with a specific location.
-
D.
hasAltarType
Indicates that an entity is associated with or characterized by a specific type or category of altar.
-
E.
hasMainAltarFor
Indicates that a specific altar serves as the primary or central altar designated for a particular entity, such as a church, chapel, or religious space.
- 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_69f76ed403208190b862dc795171353f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69feabcda59481908f2bc13b46fcced1 |
completed | May 9, 2026, 3:36 a.m. |
| PD | Predicate disambiguation | batch_69feaabd63f88190b30dcf6dd2ea39d1 |
completed | May 9, 2026, 3:32 a.m. |
Created at: May 3, 2026, 4:32 p.m.