Triple
T35133297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of Santa Maria Immacolata e San Zeno |
E1014499
|
entity |
| Predicate | hasSecondaryDedication |
P201556
|
FINISHED |
| Object | Saint Zeno |
—
|
NE NERFINISHED |
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: Saint Zeno | Statement: [Church of Santa Maria Immacolata e San Zeno, hasSecondaryDedication, Saint Zeno]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondaryDedication Context triple: [Church of Santa Maria Immacolata e San Zeno, hasSecondaryDedication, Saint Zeno]
-
A.
hasSecondaryUsage
Indicates that an entity is associated with an additional, non-primary function or purpose beyond its main intended use.
-
B.
hasSecondary
Indicates that an entity is associated with an additional or subordinate counterpart beyond its primary one.
-
C.
hasSecondaryCenter
Indicates that an entity possesses an additional, subordinate or auxiliary center beyond its primary center.
-
D.
hasSecondaryUser
Indicates that an entity is associated with an additional, non-primary user who also has access to or control over it.
-
E.
hasSecondaryStation
Indicates that an entity is associated with an additional, subordinate, or backup station beyond its primary one.
- 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_69f76dd9c1848190af70d4882a2c1ad7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a0004582bb08190b8d0b88251e8d333 |
completed | May 10, 2026, 4:06 a.m. |
| PD | Predicate disambiguation | batch_6a0003e3e5588190933beea5fb28f150 |
completed | May 10, 2026, 4:04 a.m. |
| PDg | Predicate description generation | batch_6a00045774ec81908ca607565b074f31 |
completed | May 10, 2026, 4:06 a.m. |
Created at: May 3, 2026, 4:02 p.m.