Triple
T30244499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spira |
E769018
|
entity |
| Predicate | usedInMedievalSources |
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, usedInMedievalSources, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInMedievalSources Context triple: [Spira, usedInMedievalSources, true]
-
A.
medievalAssociation
Indicates a relationship or involvement between entities specifically within a medieval context, such as shared roles, activities, or affiliations characteristic of the Middle Ages.
-
B.
isMedieval
Indicates that something belongs to, originates from, or is characteristic of the medieval (Middle Ages) period.
-
C.
medievalSignificance
Indicates that something holds notable importance, influence, or relevance within the context of the medieval period.
-
D.
medievalSeeTransferredTo
Indicates that authority, ownership, or jurisdiction over a medieval ecclesiastical see was formally transferred from one holder or location to another.
-
E.
suppressedAsMedievalSee
Indicates that a religious jurisdiction or episcopal see was discontinued or lost its status during the medieval period.
- F. None of above. chosen
Provenance (4 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_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
| PDg | Predicate description generation | batch_69fd485e0c20819099756b4fe39ac326 |
completed | May 8, 2026, 2:20 a.m. |
Created at: April 29, 2026, 7:39 p.m.