Triple
T4189943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LOM |
E89008
|
entity |
| Predicate | isUsedForPostNominals |
P1610
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [LOM, isUsedForPostNominals, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsedForPostNominals Context triple: [LOM, isUsedForPostNominals, true]
-
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.
hasInsigniaWornBy
Indicates that a particular insignia is worn by a specified entity (such as a person, group, or organization).
-
D.
heraldicStatus
Indicates the formal standing or classification of an entity within a heraldic system, such as its rank, legitimacy, or official recognition in heraldry.
-
E.
hasOfficialUse
Indicates that something is used in an authorized or formally recognized capacity, typically by an official body or for official purposes.
- 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_69aed9569a4481908b6c1fcec2a11e21 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af04b009dc8190abda3f149a5b16fa |
completed | March 9, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69af01935064819096b7619f42e164dd |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:46 p.m.