Triple
T4614813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mata |
E100841
|
entity |
| Predicate | usedInAddressForm |
P4477
|
FINISHED |
| Object | devotees addressing a 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: devotees addressing a goddess | Statement: [Mata, usedInAddressForm, devotees addressing a goddess]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInAddressForm Context triple: [Mata, usedInAddressForm, devotees addressing a goddess]
-
A.
addressFormFor
chosen
Indicates the form of address or mode of speaking that one entity should use when referring to or speaking to another entity.
-
B.
hasAddress
Indicates that an entity is associated with a specific address or location.
-
C.
canAddress
Indicates that one entity has the ability or permission to direct communication, action, or service toward another entity.
-
D.
addressFormat
Indicates the standardized structure or pattern in which an address’s components are arranged and written.
-
E.
usesAddressingSystem
Indicates that one entity employs or applies a particular addressing system associated with 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59c3d9ec8190a50ef03627dc351d |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd522e2d5c8190937d0b5574f78f99 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.