Triple
T4402967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rucouskiria Bibliasta |
E93659
|
entity |
| Predicate | approximatePublicationDate |
P877
|
FINISHED |
| Object | 1540s |
—
|
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: 1540s | Statement: [Rucouskiria Bibliasta, approximatePublicationDate, 1540s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximatePublicationDate Context triple: [Rucouskiria Bibliasta, approximatePublicationDate, 1540s]
-
A.
releaseApproximateYear
Indicates that an entity was released or made available around a specified year, where the year is approximate rather than exact.
-
B.
dateApproximate
chosen
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
C.
hasPublicationDate
Indicates that an entity is associated with the specific date on which it was published.
-
D.
lastPublicationYear
Indicates the year in which an entity’s most recent publication was released.
-
E.
publicationYear
Indicates the specific calendar year in which a work was formally published or released.
- 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_69b345158c748190a2c040fce2da9980 |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b352d08a0c8190ac6c125df40eca75 |
completed | March 12, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69b34f5b36a881909bf2e970aa523390 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:28 p.m.