Triple
T1306130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LRSM diploma |
E27881
|
entity |
| Predicate | canBeUsedAsPostnominal |
P1610
|
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: [LRSM diploma, canBeUsedAsPostnominal, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeUsedAsPostnominal Context triple: [LRSM diploma, canBeUsedAsPostnominal, yes]
-
A.
hasPostnominalLetters
Indicates that a person holds specific postnominal letters (abbreviations after their name) signifying qualifications, honors, or titles.
-
B.
hasPostNominal
chosen
Indicates that an entity is associated with a post-nominal title, abbreviation, or letters that follow a name to denote qualifications, honors, or status.
-
C.
isPersonalName
Indicates that the value is a personal name identifying an individual person.
-
D.
hasHonorificName
Indicates that an entity is referred to by a formal or respectful title or name used as an honorific.
-
E.
isOrderOfKnighthood
Indicates that an entity is a formal chivalric or knightly order to which individuals can be admitted.
- 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_69a496d7d83481908f83085854e51328 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c15490a88190872c3d2698a8f9c9 |
completed | March 1, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69a4bee9e4a88190b22ab2ee831a23c9 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:51 p.m.