Triple
T24725894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vienna manuscript |
E618148
|
entity |
| Predicate | languageOfWorkPreserved |
P17914
|
FINISHED |
| Object | Italian |
—
|
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: Italian | Statement: [Vienna manuscript, languageOfWorkPreserved, Italian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfWorkPreserved Context triple: [Vienna manuscript, languageOfWorkPreserved, Italian]
-
A.
languageAttestedIn
Indicates that evidence exists showing the use or presence of a particular language in a specified place, time, or context.
-
B.
languageOfHistoricalRecord
Indicates the language in which a given historical record is written or recorded.
-
C.
isWorkingLanguageOf
Indicates that a particular language is officially used as a medium of work, communication, or operation within a specified organization, institution, or context.
-
D.
languageOfWritings
chosen
Indicates that a specified language is the one in which certain writings or written works are composed.
-
E.
isLanguageOf
Indicates that a particular language is used as the official or primary language associated with a given entity (such as a person, document, or region).
- 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_69e2fab772608190b74163751047ff50 |
completed | April 18, 2026, 3:29 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
Created at: April 18, 2026, 3:57 a.m.