Triple
T25074637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baba Marta |
E628012
|
entity |
| Predicate | folkBelief |
P138663
|
FINISHED |
| Object | Baba Marta controls the weather in March |
—
|
NE NERFINISHED |
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: Baba Marta controls the weather in March | Statement: [Baba Marta, folkBelief, Baba Marta controls the weather in March]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: folkBelief Context triple: [Baba Marta, folkBelief, Baba Marta controls the weather in March]
-
A.
folkloreFunction
Indicates that something serves a role, purpose, or function within a body of folklore, such as myths, legends, or traditional narratives.
-
B.
superstitionType
Indicates the specific category or kind of superstition associated with an entity or belief.
-
C.
hasSuperstition
Indicates that one entity holds or practices a particular superstition related to another entity or concept.
-
D.
countryOfFolklore
Indicates the country with which a particular piece or tradition of folklore is associated or from which it originates.
-
E.
domainOfBelief
chosen
Indicates the conceptual area or subject matter that a particular belief pertains to or is about.
- 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f45d188208819095eae1c605b12df0 |
completed | May 1, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
Created at: April 18, 2026, 6:20 a.m.