Triple
T10675558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pazzi Conspiracy |
E251606
|
entity |
| Predicate | hasSpecificDate |
P6878
|
FINISHED |
| Object | 26 April 1478 |
—
|
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: 26 April 1478 | Statement: [Pazzi Conspiracy, hasSpecificDate, 26 April 1478]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpecificDate Context triple: [Pazzi Conspiracy, hasSpecificDate, 26 April 1478]
-
A.
hasDateWith
Indicates that one entity is scheduled to go on or is engaged in a romantic or social date with another entity.
-
B.
hasBaseDate
Indicates that an entity is associated with a specific reference or starting date used as the basis for related calculations, schedules, or validity periods.
-
C.
hasDateInGregorianCalendar
Indicates that an entity is associated with a specific date expressed using the Gregorian calendar system.
-
D.
hasKeyDate
Indicates a relationship where an entity is associated with an important or significant date relevant to its status, lifecycle, or context.
-
E.
dateOf
chosen
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
- 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_69d6aa5b0d2881909584b20efc5877f0 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fb935ca88190b1312d3d53902af5 |
completed | April 9, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8a93208190a573061387e2aebb |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:09 p.m.