Triple
T26288234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wahlstatt |
E661196
|
entity |
| Predicate | linkedNobility |
P13617
|
FINISHED |
| Object | Prussian 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: Prussian nobility | Statement: [Wahlstatt, linkedNobility, Prussian nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedNobility Context triple: [Wahlstatt, linkedNobility, Prussian nobility]
-
A.
linkedToPeerage
Indicates that one entity has an established connection or association with a system of peerage or noble titles.
-
B.
associatedNobleFamily
chosen
Indicates a relationship where an entity is linked or connected to a particular noble family, typically by heritage, allegiance, or formal association.
-
C.
associatedNobleRank
Indicates that an entity is linked to or holds a particular noble rank or title.
-
D.
involvedNobility
Indicates that the entities participated in or were associated with an event, action, or situation in the capacity of nobility or aristocratic status.
-
E.
associatedNobleTitle
Indicates that an entity is linked to or bears a particular noble or aristocratic title.
- 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_69ee812bbd448190be4d7478b057990a |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 26, 2026, 10:06 p.m.