Triple
T24918569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VSM |
E624056
|
entity |
| Predicate | usedInNameStyle |
P81832
|
FINISHED |
| Object | placed after the recipient’s name as post-nominal letters |
—
|
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: placed after the recipient’s name as post-nominal letters | Statement: [VSM, usedInNameStyle, placed after the recipient’s name as post-nominal letters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInNameStyle Context triple: [VSM, usedInNameStyle, placed after the recipient’s name as post-nominal letters]
-
A.
usedInNamingPractice
Indicates that something serves as a basis, source, or reference in the practice of assigning names.
-
B.
styleNameUsage
chosen
Indicates how a particular style name is applied or used in relation to an entity or context.
-
C.
nameUsedIn
Indicates that a particular name is employed or referenced within a specified context, work, or usage setting.
-
D.
usedInFullNameOf
Indicates that one entity (such as a word, name part, or title) is used as a component within the complete formal name of another entity.
-
E.
nameStyle
Indicates how an entity’s name is formatted or stylistically presented (e.g., capitalization, punctuation, or naming convention).
- 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_69e2fac889c081908e9ff686cb428e5a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
Created at: April 18, 2026, 5:28 a.m.