Triple
T29899443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pazzi family |
E759369
|
entity |
| Predicate | hasAncestralChapel |
P34531
|
FINISHED |
| Object | Pazzi Chapel |
—
|
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: Pazzi Chapel | Statement: [Pazzi family, hasAncestralChapel, Pazzi Chapel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAncestralChapel Context triple: [Pazzi family, hasAncestralChapel, Pazzi Chapel]
-
A.
hasChapels
chosen
Indicates that one entity contains, includes, or is associated with one or more chapels.
-
B.
hasChapelLocation
Indicates that one entity serves as the physical location or site where a chapel associated with another entity is situated.
-
C.
hasChapelNearby
Indicates that one entity is located close to or in the vicinity of a chapel.
-
D.
hasPilgrimageChurch
Indicates that a location or entity possesses or is associated with a church that serves as a destination for religious pilgrimage.
-
E.
hasChapelHonoring
Indicates that one entity contains or includes a chapel dedicated to honoring another entity.
- 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_69f2245f1cf88190978c70d1a1d2cb73 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 29, 2026, 6:06 p.m.