Triple
T30244517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spira |
E769018
|
entity |
| Predicate | wasImperialDietLocation |
P169379
|
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, wasImperialDietLocation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasImperialDietLocation Context triple: [Spira, wasImperialDietLocation, true]
-
A.
hasPositionInImperialDiet
Indicates that an entity holds or held a formal seat or role within the Imperial Diet.
-
B.
hasImperialPalace
Indicates that an entity possesses or is the location of an official imperial palace.
-
C.
heldInEmpire
Indicates that an event, position, or status occurred or existed within the territorial or political bounds of a particular empire.
-
D.
servedAsImperialResidenceFrom
Indicates that an entity functioned as an imperial residence starting from a specified point in time.
-
E.
hadImperialCircle
Indicates that an entity was administratively organized within a specific Imperial Circle of the Holy Roman Empire.
- 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_69f68074f0d081909ac1a54ff5f3797d |
completed | May 2, 2026, 10:53 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67d31cc60819084f64bd056e1ea4d |
completed | May 2, 2026, 10:39 p.m. |
Created at: April 29, 2026, 7:39 p.m.