Triple
T28989081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanctuary of the Beata Vergine del Soccorso |
E734772
|
entity |
| Predicate | hasChapelCount |
P34531
|
FINISHED |
| Object | 14 |
—
|
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: 14 | Statement: [Sanctuary of the Beata Vergine del Soccorso, hasChapelCount, 14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChapelCount Context triple: [Sanctuary of the Beata Vergine del Soccorso, hasChapelCount, 14]
-
A.
hasChapelCountApprox
Indicates an approximate number of chapels associated with an entity.
-
B.
hasChapels
chosen
Indicates that one entity contains, includes, or is associated with one or more chapels.
-
C.
hasChapelLocation
Indicates that one entity serves as the physical location or site where a chapel associated with another entity is situated.
-
D.
hasChapelUse
Indicates that something is used, designated, or functions as a chapel or for chapel-related purposes.
-
E.
hasChapelStatus
Indicates that an entity holds a designated status or classification specifically related to a chapel.
- 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_69f05b0dd9b481908b7901e1c95ff6b2 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: April 28, 2026, 9:16 a.m.