Triple
T18428473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Llorona (Chilote variant) |
E450199
|
entity |
| Predicate | encounterType |
P91146
|
FINISHED |
| Object | nocturnal apparition |
—
|
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: nocturnal apparition | Statement: [La Llorona (Chilote variant), encounterType, nocturnal apparition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encounterType Context triple: [La Llorona (Chilote variant), encounterType, nocturnal apparition]
-
A.
encounterLocation
Indicates the place or setting where two or more entities meet, interact, or come into contact.
-
B.
encountered
Indicates that one entity came across or met another entity, typically in a specific place or context, often unexpectedly or during the course of some activity.
-
C.
typicalVisitType
chosen
Indicates the usual or most common category of visit associated with an entity or event.
-
D.
admissionType
Indicates the category or manner in which an entity (such as a person or case) is formally accepted or admitted into a system, institution, or process.
-
E.
interventionType
Indicates the specific kind or category of action, treatment, or measure applied in an intervention.
- 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51b14c4d481909af975575a43c4e1 |
completed | April 19, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69e469bf7f74819096a01173493412c2 |
completed | April 19, 2026, 5:35 a.m. |
Created at: April 10, 2026, 11:25 a.m.