Triple
T29893404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dadasaheb |
E759213
|
entity |
| Predicate | typicalAddressees |
P10804
|
FINISHED |
| Object | elder men |
—
|
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: elder men | Statement: [Dadasaheb, typicalAddressees, elder men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAddressees Context triple: [Dadasaheb, typicalAddressees, elder men]
-
A.
addresseeType
Indicates the role or category of the entity that is the intended recipient or target of a communication or message.
-
B.
typicalMembers
Indicates that the related entities are representative or characteristic members of a larger group, category, or class.
-
C.
normAddressee
Indicates that a particular entity is the socially or conventionally appropriate recipient or target of an utterance, message, or communicative act.
-
D.
typicalAudience
chosen
Indicates the group of people for whom something (such as a work, product, or resource) is primarily intended or most suitable.
-
E.
addresseeOf
Indicates that one entity is the intended recipient or target audience of a communication, message, or expression from 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_69f2245f1cf88190978c70d1a1d2cb73 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a031045669c8190944781a48d09b5b6 |
completed | May 12, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_6a030fa775848190839b388f950d0364 |
completed | May 12, 2026, 11:31 a.m. |
Created at: April 29, 2026, 6:03 p.m.