Triple
T9763763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chief Master Sergeant |
E236731
|
entity |
| Predicate | typicalAddressedAs |
P743
|
FINISHED |
| Object | Chief |
—
|
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: Chief | Statement: [Chief Master Sergeant, typicalAddressedAs, Chief]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAddressedAs Context triple: [Chief Master Sergeant, typicalAddressedAs, Chief]
-
A.
addressingType
Indicates the manner or form in which one entity addresses or refers to another (e.g., formally, informally, by title, or by name).
-
B.
honorificNickname
chosen
Indicates that one entity is referred to by a respectful or honorific nickname by another entity or in a given context.
-
C.
hasAffectionateNicknameFor
Indicates that one entity uses or assigns a fond, affectionate, or endearing nickname to another entity.
-
D.
normAddressee
Indicates that a particular entity is the socially or conventionally appropriate recipient or target of an utterance, message, or communicative act.
-
E.
honorificTitleGivenBy
Indicates that an honorific title is formally conferred on one entity by another entity.
- 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_69ca84d64f6c8190a4ed4e9f5936eda5 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda09d8bc88190808145f141b4a9f8 |
completed | April 1, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69cd03d0772c8190bd1750cf1cfba309 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:25 p.m.