Triple
T10258671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISTC (Incunabula Short Title Catalogue) |
E240538
|
entity |
| Predicate | temporalScopeEnd |
P140
|
FINISHED |
| Object | 1500 |
—
|
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: 1500 | Statement: [ISTC (Incunabula Short Title Catalogue), temporalScopeEnd, 1500]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporalScopeEnd Context triple: [ISTC (Incunabula Short Title Catalogue), temporalScopeEnd, 1500]
-
A.
temporalAuthorityEndedBy
Indicates that a period of temporal authority or secular power held by one entity comes to an end as a result of an action or event caused by another entity.
-
B.
typicallyEndsAt
Indicates that an event, process, or activity most commonly or usually concludes at a particular time, place, or state.
-
C.
focusPeriodEnd
Indicates the point in time at which a specified focus period or interval concludes.
-
D.
timePeriodEndApprox
Indicates that the associated time period ends at an approximate, rather than exact, point in time.
-
E.
endDate
chosen
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
- 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_69d381a7e198819090280d5ab885d59e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2b5853081909cd0397e08a0f44d |
completed | April 7, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69d4d1edae6881909a65201b8e51ea0a |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:31 a.m.