Triple
T36066587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chiesa di Santa Maria in Monticelli |
E1043247
|
entity |
| Predicate | hasSingleNave |
P21022
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Chiesa di Santa Maria in Monticelli, hasSingleNave, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSingleNave Context triple: [Chiesa di Santa Maria in Monticelli, hasSingleNave, yes]
-
A.
hasNave
chosen
Indicates that one entity (typically a building or structure) possesses or includes a nave as a distinct architectural part.
-
B.
hasSingle
Indicates that an entity possesses exactly one instance of a specified related entity or attribute.
-
C.
isSingle
Indicates that an entity is not currently in a romantic relationship or legally married.
-
D.
hasSingleHall
Indicates that an entity possesses exactly one hall within its structure or domain.
-
E.
hasNavePlan
Indicates that an entity possesses or is associated with a specific plan or layout for a nave (the central part of a church or similar building).
- 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_69f76e2fd3248190b900d9a492bf5a7a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe08d2b2e48190ac7be6d62d4a44a3 |
completed | May 8, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69fe06cd3af08190ae25de0dc0cdd573 |
completed | May 8, 2026, 3:52 p.m. |
Created at: May 3, 2026, 4:08 p.m.