Triple
T30244508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spira |
E769018
|
entity |
| Predicate | hasAlternativeMedievalForm |
P135558
|
FINISHED |
| Object | Spirae |
—
|
NE NERFINISHED |
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: Spirae | Statement: [Spira, hasAlternativeMedievalForm, Spirae]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternativeMedievalForm Context triple: [Spira, hasAlternativeMedievalForm, Spirae]
-
A.
isMedievalForm
chosen
Indicates that one form or variant of something is specifically the medieval version of another form or of a general concept.
-
B.
hasMedievalNameBasis
Indicates that something derives its name from, or is based on, a name used in the medieval period.
-
C.
isModernFormOf
Indicates that one entity is a newer or contemporary version, adaptation, or evolution of another earlier entity.
-
D.
hasAlternativeToponymy
Indicates that an entity is associated with one or more alternative place names or toponyms used to refer to the same geographic location.
-
E.
medievalSeeTransferredTo
Indicates that authority, ownership, or jurisdiction over a medieval ecclesiastical see was formally transferred from one holder or location to another.
- 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_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 29, 2026, 7:39 p.m.