Triple
T21704490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quanta Cura |
E535737
|
entity |
| Predicate | dateOfAssociatedDocument |
P6878
|
FINISHED |
| Object | 8 December 1864 |
—
|
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: 8 December 1864 | Statement: [Quanta Cura, dateOfAssociatedDocument, 8 December 1864]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfAssociatedDocument Context triple: [Quanta Cura, dateOfAssociatedDocument, 8 December 1864]
-
A.
issuedDocumentDate
Indicates the date on which a document was formally created, released, or made officially valid by the issuing party.
-
B.
documentDraftedAt
Indicates the time or place at which a document was initially drafted or created.
-
C.
dateOf
chosen
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
D.
dateSigned
Indicates the specific date on which an agreement, document, or contract was formally signed.
-
E.
accessionDate
Indicates the date on which an item, record, or entity was formally added to a collection, system, or repository.
- 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_69e0c46b44c0819088ab883ebd44e0e8 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efb52e4b84819095a24cc9fdca2b8a |
completed | April 27, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69e6969113cc8190ab69855ef5667e4b |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:46 p.m.