Triple
T967945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Textus Receptus |
E20878
|
entity |
| Predicate | firstEditionPublishedIn |
P18405
|
FINISHED |
| Object | 1516 |
—
|
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: 1516 | Statement: [Textus Receptus, firstEditionPublishedIn, 1516]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstEditionPublishedIn Context triple: [Textus Receptus, firstEditionPublishedIn, 1516]
-
A.
firstEditionPublicationYear
chosen
Indicates the year in which an entity’s first edition was originally published.
-
B.
firstEditionType
Indicates that an entity is classified as a first edition of a work, specifying the type or category of that first edition.
-
C.
firstPublisher
Indicates that an entity is the original or earliest publisher of another entity (such as a work, edition, or resource).
-
D.
firstCompleteEditionPlace
Indicates the place where the first complete edition of a work was published or produced.
-
E.
placeOfFirstPublication
Indicates the location where a work was first published or made publicly available.
- 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_69a493b33d2c81909c52c369d3ca8436 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b43549008190a4d65efdc3bda520 |
completed | March 1, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a42c1481908d940cbe0aefdd3b |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.