Triple
T9350958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince-Bishopric of Speyer |
E225015
|
entity |
| Predicate | hasNobility |
P68122
|
FINISHED |
| Object | local ministeriales and lesser nobility |
—
|
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: local ministeriales and lesser nobility | Statement: [Prince-Bishopric of Speyer, hasNobility, local ministeriales and lesser nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNobility Context triple: [Prince-Bishopric of Speyer, hasNobility, local ministeriales and lesser nobility]
-
A.
hasNobleStatus
Indicates that an entity possesses a recognized noble rank, title, or aristocratic status.
-
B.
hasNoble
chosen
Indicates that one entity possesses or is associated with a noble title, status, or noble individual.
-
C.
nobilityClass
Indicates that an entity belongs to, or is associated with, a particular class or rank within a nobility hierarchy.
-
D.
hasNobilityParticle
Indicates that a person’s name includes a nobility particle (such as “von,” “de,” or “van”) signifying noble or aristocratic status.
-
E.
nobilitySystem
Indicates a social or political structure in which individuals are ranked by hereditary titles or noble status.
- 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_69ca842abfd48190949d71c3b86eeba8 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd4f9248c08190a7bb40feec2eb217 |
completed | April 1, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69cc7a68ab9481909f97cb70764697cc |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:41 p.m.