Triple
T532796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KCSI |
E12259
|
entity |
| Predicate | usedAsPostNominalLetters |
P1600
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [KCSI, usedAsPostNominalLetters, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsPostNominalLetters Context triple: [KCSI, usedAsPostNominalLetters, yes]
-
A.
hasPostnominalLetters
Indicates that a person holds specific postnominal letters (abbreviations after their name) signifying qualifications, honors, or titles.
-
B.
honorificSuffix
Indicates that one entity is a respectful or formal suffix appended to another entity’s name or title.
-
C.
postNominalLetters
chosen
Indicates that a person is associated with specific letters placed after their name to denote qualifications, honors, or professional affiliations.
-
D.
hasPostNominal
Indicates that an entity is associated with a post-nominal title, abbreviation, or letters that follow a name to denote qualifications, honors, or status.
-
E.
honorificPrefix
Indicates the formal title or respectful prefix (e.g., "Dr.", "Mr.", "Prof.") used before a person's name to denote status, role, or honor.
- 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_69a4933208e88190891f5debab1b776d |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4985e51908190a34aa82ea9dbee1e |
completed | March 1, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69a494b3e49081909810fa417b31306f |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.