Triple
T18831858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annals of Fulda |
E460551
|
entity |
| Predicate | chronicleEndYear |
P129764
|
FINISHED |
| Object | 901 |
—
|
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: 901 | Statement: [Annals of Fulda, chronicleEndYear, 901]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronicleEndYear Context triple: [Annals of Fulda, chronicleEndYear, 901]
-
A.
chroniclesEndDate
Indicates the date on which a chronicle, record, or documented series of events concludes.
-
B.
chronologicalCoverageEnd
chosen
Indicates the point in time at which the temporal or chronological span of something (such as a resource, event, or record) comes to an end.
-
C.
chronologyEnd
Indicates that one event, state, or time interval marks the ending point or conclusion of another in a temporal sequence.
-
D.
chroniclesPeriodFrom
Indicates that something documents or records events starting from a specified point in time or historical period.
-
E.
yearOfCreationEnd
Indicates the year in which the creation or production of something was completed or came 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_69d8dcf94c288190a06dea029ae4b223 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5a99a792c81908b9a0741ef6ee782 |
completed | April 20, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.