Triple
T8014453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | von Bock |
E186575
|
entity |
| Predicate | hasNobilityAssociation |
P58699
|
FINISHED |
| Object | German 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: German nobility | Statement: [von Bock, hasNobilityAssociation, German nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNobilityAssociation Context triple: [von Bock, hasNobilityAssociation, German nobility]
-
A.
associatedWithNobilityConceptually
Indicates a conceptual or symbolic connection between something and nobility, such as aristocratic status, noble qualities, or related social class ideas.
-
B.
hasNobleStatus
Indicates that an entity possesses a recognized noble rank, title, or aristocratic status.
-
C.
associatedNobleRank
Indicates that an entity is linked to or holds a particular noble rank or title.
-
D.
hasNoble
Indicates that one entity possesses or is associated with a noble title, status, or noble individual.
-
E.
hasNobilityParticle
chosen
Indicates that a person’s name includes a nobility particle (such as “von,” “de,” or “van”) signifying noble or aristocratic 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_69ca82ac7fc081909b1398cf025423af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3df0f4bc8190ae87586972018085 |
completed | March 31, 2026, 3:22 a.m. |
| PD | Predicate disambiguation | batch_69cb048c9f488190b4fb8917a9c21bc5 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:19 p.m.