Triple
T11796971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | dilogún |
E280525
|
entity |
| Predicate | practitionerCalled |
P2458
|
FINISHED |
| Object | santero |
—
|
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: santero | Statement: [dilogún, practitionerCalled, santero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: practitionerCalled Context triple: [dilogún, practitionerCalled, santero]
-
A.
nowCalled
Indicates that an entity previously known by one name is currently referred to by a different name.
-
B.
holderCalled
Indicates that one entity, acting as a holder or possessor, initiated a phone call or communication to another entity.
-
C.
calledAs
Indicates that one entity is referred to, named, or addressed by another specific name or label.
-
D.
associatedWithPractice
chosen
Indicates a relationship in which an entity is connected or linked to a particular practice, activity, or customary way of doing something.
-
E.
calledBy
Indicates that one entity initiates a call or invocation to 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5a1cda0819092d66a82fd882786 |
completed | April 10, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69d8a2491f048190853239bc05090bf4 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.