Triple
T5206087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cathedral Library, Vercelli |
E117513
|
entity |
| Predicate | languageOfNotableManuscripts |
P17914
|
FINISHED |
| Object | Old English |
—
|
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: Old English | Statement: [Cathedral Library, Vercelli, languageOfNotableManuscripts, Old English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfNotableManuscripts Context triple: [Cathedral Library, Vercelli, languageOfNotableManuscripts, Old English]
-
A.
languageOfWritings
chosen
Indicates that a specified language is the one in which certain writings or written works are composed.
-
B.
languageOfHistoricalRecord
Indicates the language in which a given historical record is written or recorded.
-
C.
languageOfBooks
Indicates the language in which the referenced books are written or published.
-
D.
inscriptionsLanguage
Indicates that the language used in the inscriptions on an object or surface is the specified language.
-
E.
notableManuscriptFeature
Indicates that a manuscript possesses a specific distinguishing characteristic, attribute, or element that is considered noteworthy or significant.
- 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_69bd4463dd3c81909966123f20b79d57 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7a490338819080481df79d3aae01 |
completed | March 20, 2026, 4:48 p.m. |
| PD | Predicate disambiguation | batch_69bd77bb4e8c819094b5ac7cf61512f9 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:47 p.m.