Triple
T35227120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maiya |
E1017127
|
entity |
| Predicate | typicalAddressee |
P42663
|
FINISHED |
| Object | local village goddess |
—
|
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: local village goddess | Statement: [Maiya, typicalAddressee, local village goddess]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAddressee Context triple: [Maiya, typicalAddressee, local village goddess]
-
A.
normAddressee
chosen
Indicates that a particular entity is the socially or conventionally appropriate recipient or target of an utterance, message, or communicative act.
-
B.
addresseeType
Indicates the role or category of the entity that is the intended recipient or target of a communication or message.
-
C.
addresseeDescription
Indicates that one entity provides a descriptive characterization or identifying information about the addressee of a communication or message.
-
D.
addresseeOf
Indicates that one entity is the intended recipient or target audience of a communication, message, or expression from another entity.
-
E.
typicalDestinationAddress
Indicates the address that is most commonly or usually used as the destination for something or someone.
- 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_69f76de12e4c8190bc46b71a32858356 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:02 p.m.