Triple
T19428048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FSA |
E486034
|
entity |
| Predicate | postnominalPosition |
P1610
|
FINISHED |
| Object | after the holder’s name |
—
|
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: after the holder’s name | Statement: [FSA, postnominalPosition, after the holder’s name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postnominalPosition Context triple: [FSA, postnominalPosition, after the holder’s name]
-
A.
namedAfterPosition
Indicates that an entity is named after a specific position, role, or rank associated with it.
-
B.
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).
-
C.
namePosition
Indicates the positional or ordering relationship of a name within a sequence or structured context (e.g., first, last, or specific index).
-
D.
postNominalCategory
Indicates a classification or type assigned to an entity that is expressed in a post-nominal position (after the name or noun).
-
E.
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.
- 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6321abb9c81908ad73c2cd537d0f1 |
completed | April 20, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:37 p.m.