Triple
T33264558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Universal Short Title Catalogue |
E851609
|
entity |
| Predicate | coversToYear |
P98851
|
FINISHED |
| Object | 1700 |
—
|
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: 1700 | Statement: [Universal Short Title Catalogue, coversToYear, 1700]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversToYear Context triple: [Universal Short Title Catalogue, coversToYear, 1700]
-
A.
coversFromYear
Indicates that something (such as a record, dataset, or agreement) applies starting from a specified year onward.
-
B.
coversYearsTo
chosen
Indicates a temporal relationship where one entity spans, includes, or extends up to a specified year or range of years represented by the other entity.
-
C.
coversTo
Indicates that one entity extends its coverage or protective scope to include another entity.
-
D.
coversFrom
Indicates that one entity provides protection, concealment, or shelter for another entity against something originating from a specified source or direction.
-
E.
endYearCovered
Indicates the year in which a specified coverage, period, or applicability comes to an end.
- 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_69f349642dac81908a37ffcc3b976a55 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 1, 2026, 1:32 a.m.