Triple
T532772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GCSI |
E12258
|
entity |
| Predicate | postNominalCategory |
P16520
|
FINISHED |
| Object | chivalric honour |
—
|
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: chivalric honour | Statement: [GCSI, postNominalCategory, chivalric honour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postNominalCategory Context triple: [GCSI, postNominalCategory, chivalric honour]
-
A.
postNominalLetters
Indicates that a person is associated with specific letters placed after their name to denote qualifications, honors, or professional affiliations.
-
B.
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.
-
C.
postTown
Indicates the town or locality that serves as the postal address destination for a given address or location.
-
D.
postalService
Indicates a relationship where one entity provides or manages the delivery and handling of mail and packages for another entity.
-
E.
postalArea
Indicates that one entity is the postal or ZIP code area associated with the location or address represented by the other entity.
- 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_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. |
| PDg | Predicate description generation | batch_69a49857e1148190aa782b82675cf0b5 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:32 p.m.