Triple
T30244506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spira |
E769018
|
entity |
| Predicate | usedInMedievalLatinCharters |
P193478
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Spira, usedInMedievalLatinCharters, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInMedievalLatinCharters Context triple: [Spira, usedInMedievalLatinCharters, true]
-
A.
usedInMedievalSources
chosen
Indicates that something is referenced or attested in documents or sources from the medieval period.
-
B.
medievalSeeTransferredTo
Indicates that authority, ownership, or jurisdiction over a medieval ecclesiastical see was formally transferred from one holder or location to another.
-
C.
isMedievalForm
Indicates that one form or variant of something is specifically the medieval version of another form or of a general concept.
-
D.
medievalStatus
Indicates the social, legal, or hierarchical standing an entity holds within a medieval societal structure.
-
E.
usedLanguageInChancery
Indicates that a particular language was employed as the official medium of writing and record-keeping in a chancery or administrative office.
- 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_69f224831dc08190b2e569b987264057 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: April 29, 2026, 7:39 p.m.