Triple
T32965637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anton Koberger |
E843358
|
entity |
| Predicate | timePeriodOfActivityEnd |
P35259
|
FINISHED |
| Object | early 16th century |
—
|
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: early 16th century | Statement: [Anton Koberger, timePeriodOfActivityEnd, early 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodOfActivityEnd Context triple: [Anton Koberger, timePeriodOfActivityEnd, early 16th century]
-
A.
eventEndTime
Indicates the specific time at which an event concludes or is considered finished.
-
B.
typicallyEndsAt
Indicates that an event, process, or activity most commonly or usually concludes at a particular time, place, or state.
-
C.
endOfActivity
Indicates that a particular activity has reached its completion or final point in time.
-
D.
timePeriodEndApprox
chosen
Indicates that the associated time period ends at an approximate, rather than exact, point in time.
-
E.
organizedEventEndTime
Indicates the time at which an organized event is scheduled or recorded to 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_69f3494af2808190ad98cec2f1bc0fe6 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 1, 2026, 1:21 a.m.