Triple
T22225204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | von Teuffenbach |
E549319
|
entity |
| Predicate | hasNobiliaryParticle |
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 Teuffenbach, hasNobiliaryParticle, von]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNobiliaryParticle Context triple: [von Teuffenbach, hasNobiliaryParticle, von]
-
A.
hasDiscourseParticle
Indicates that one element functions as a discourse particle in relation to another within a communicative or textual context.
-
B.
hasNobilityParticle
chosen
Indicates that a person’s name includes a nobility particle (such as “von,” “de,” or “van”) signifying noble or aristocratic status.
-
C.
hasNoun
Indicates that an entity possesses or is associated with a specific noun as an attribute, label, or grammatical component.
-
D.
hasParticiple
Indicates that one entity is associated with the participle form (verbal adjective or non-finite verb form) of another entity.
-
E.
hasNounIncorporation
Indicates that a verb incorporates a noun root or stem into its own form, forming a single complex predicate that expresses both the action and its nominal participant.
- 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_69e11e403d6481909a94d0aaf157f6ef |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12b93e2208190aee70ffd82962ea0 |
completed | April 28, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69e71b4dcc408190a30429fb08fcf39e |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:37 p.m.