Triple
T20380542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | von Below |
E497812
|
entity |
| Predicate | nobilityParticle |
P58699
|
FINISHED |
| Object | von |
—
|
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: von | Statement: [von Below, nobilityParticle, von]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nobilityParticle Context triple: [von Below, nobilityParticle, von]
-
A.
hasNobilityParticle
chosen
Indicates that a person’s name includes a nobility particle (such as “von,” “de,” or “van”) signifying noble or aristocratic status.
-
B.
nobilityClass
Indicates that an entity belongs to, or is associated with, a particular class or rank within a nobility hierarchy.
-
C.
nobilitySystem
Indicates a social or political structure in which individuals are ranked by hereditary titles or noble status.
-
D.
nobilityCulture
Indicates a relationship where a group’s customs, values, or practices are specifically associated with or characteristic of the nobility.
-
E.
hasNoble
Indicates that one entity possesses or is associated with a noble title, status, or noble individual.
- 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_69e0b4a5b7908190a972e4e7e698ae94 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e678b026e081909541e545886c8380 |
completed | April 20, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69e57648be3c81908256838228cabf5c |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:27 a.m.