Triple
T26288232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wahlstatt |
E661196
|
entity |
| Predicate | usedInNobleTitleOf |
P47585
|
FINISHED |
| Object | Gebhard Leberecht von Blücher |
—
|
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: Gebhard Leberecht von Blücher | Statement: [Wahlstatt, usedInNobleTitleOf, Gebhard Leberecht von Blücher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInNobleTitleOf Context triple: [Wahlstatt, usedInNobleTitleOf, Gebhard Leberecht von Blücher]
-
A.
nobleTitleOrStatus
Indicates that one entity holds, claims, or is associated with a particular noble rank, title, or social status in relation to another entity.
-
B.
nobleTitleElevated
Indicates that an entity’s noble rank or title has been raised to a higher level of nobility.
-
C.
aristocraticTitleIn
Indicates that an entity holds or is associated with a specific aristocratic or noble title within a particular jurisdiction or context.
-
D.
associatedNobleTitle
Indicates that an entity is linked to or bears a particular noble or aristocratic title.
-
E.
nobleTitleFrom
chosen
Indicates that a person derives or holds their noble title from a specified source, such as a place, lineage, or authority.
- 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_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 26, 2026, 10:06 p.m.