Triple
T31017004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Worms |
E790349
|
entity |
| Predicate | grantedImperialStatus |
P143768
|
FINISHED |
| Object | High Middle Ages |
—
|
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: High Middle Ages | Statement: [Worms, grantedImperialStatus, High Middle Ages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grantedImperialStatus Context triple: [Worms, grantedImperialStatus, High Middle Ages]
-
A.
hadImperialStatus
chosen
Indicates that an entity possessed or was granted imperial rank, authority, or official status within an empire.
-
B.
grantedToEmperor
Indicates that something (such as a right, title, privilege, or possession) has been formally given or conferred to an emperor.
-
C.
grantedImperialImmediacyBy
Indicates that an entity received the special legal-political status of imperial immediacy directly from a specified imperial authority.
-
D.
wasMadeCoEmperorBy
Indicates that one entity was elevated to the rank of co-emperor through the action or decision of another entity.
-
E.
establishedAsImperialEstate
Indicates that something has been formally designated or set up as an imperial estate under the authority of an empire.
- 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 29, 2026, 8:58 p.m.