Triple
T1254508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mass of St. Pius V |
E26955
|
entity |
| Predicate | standardEditionYear |
P7939
|
FINISHED |
| Object | 1570 |
—
|
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: 1570 | Statement: [Mass of St. Pius V, standardEditionYear, 1570]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardEditionYear Context triple: [Mass of St. Pius V, standardEditionYear, 1570]
-
A.
hasFirstEditionYear
Indicates the year in which the first edition of an item (such as a work, book, or publication) was originally released or published.
-
B.
introducedInYear
Indicates the year in which something was first introduced, launched, or made available.
-
C.
standardizedInYear
chosen
Indicates the specific year in which something was formally standardized or adopted as a standard.
-
D.
lastLifetimeEditionYear
Indicates the year in which the most recent lifetime edition of an entity (such as a work or product) was issued or became available.
-
E.
accessionYear
Indicates the calendar year in which an item, record, or entity was formally added to or registered within a collection, system, or institution.
- 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_69a49487a9c48190ba9b05348fd1b53f |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bfa5a4cc819093ed686619b572d8 |
completed | March 1, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6c977c8190a2bf3e8b67a59beb |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.