Triple
T35594451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albert of Mainz |
E1028587
|
entity |
| Predicate | sentDocument |
P36417
|
FINISHED |
| Object | Ninety-five Theses |
—
|
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: Ninety-five Theses | Statement: [Albert of Mainz, sentDocument, Ninety-five Theses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sentDocument Context triple: [Albert of Mainz, sentDocument, Ninety-five Theses]
-
A.
sentDocumentTo
chosen
Indicates that one entity transmitted or delivered a document to another entity.
-
B.
sentIn
Indicates that something (such as a message, document, or item) was transmitted or dispatched to a recipient or destination at a particular time or via a particular medium.
-
C.
receivedDocument
Indicates that one entity has been given and taken possession of a document from another entity or source.
-
D.
sentAs
Indicates that one entity was transmitted, dispatched, or delivered in the form, role, or capacity of another (e.g., an item or message being sent as something specific).
-
E.
sentAfter
Indicates that one message or item was sent at a later time than another specified message or item.
- 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_69f76e0598dc8190a6a093e904b9aa70 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec355048190af30123ceb6efa2b |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.