Triple
T21179828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baronet Montgomery |
E521916
|
entity |
| Predicate | entailsPostnominal |
P143185
|
FINISHED |
| Object | Bt |
—
|
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: Bt | Statement: [Baronet Montgomery, entailsPostnominal, Bt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entailsPostnominal Context triple: [Baronet Montgomery, entailsPostnominal, Bt]
-
A.
hasPostnominalLetters
Indicates that a person holds specific postnominal letters (abbreviations after their name) signifying qualifications, honors, or titles.
-
B.
usesPostNominalsIn
Indicates that an entity customarily appends specific post-nominal letters to its name within a given context or jurisdiction.
-
C.
nonPostNominal
Indicates that the related element does not appear in a post-nominal position (i.e., it does not follow the noun it modifies or relates to).
-
D.
namedAfter
Indicates that one entity has been given its name in honor of, or derived from, another entity.
-
E.
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.
- F. None of above. chosen
Provenance (4 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_69e0b50ef1d48190b063aa342667df22 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7301c842c8190b969a8b3f194003a |
completed | April 21, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f993240c8190847c0b08e65726c8 |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 3:01 p.m.