Triple
T19353002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carl von Clausewitz |
E484069
|
entity |
| Predicate | nobleParticle |
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: [Carl von Clausewitz, nobleParticle, von]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nobleParticle Context triple: [Carl von Clausewitz, nobleParticle, 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.
nobleMetal
Indicates that the subject is classified as a noble (chemically inert and corrosion-resistant) metal.
-
C.
honorificParticle
Indicates that a grammatical particle is used to convey respect, politeness, or social status toward a referent in the expression.
-
D.
usedParticle
Indicates that one entity employs or applies a particular particle (e.g., subatomic, linguistic, or material) in some process, context, or construction involving another entity.
-
E.
nobleAssembly
Indicates that an entity participates in or is associated with a formal gathering or council of nobles.
- 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_69d8e8d244f8819080eb1f3491300db2 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e61905b16881909ab0e932bb9a0cda |
completed | April 20, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69e4dd13a8cc81909cd02668564c9f29 |
completed | April 19, 2026, 1:48 p.m. |
Created at: April 10, 2026, 1:34 p.m.