Triple
T37992114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Logun Ede |
E947844
|
entity |
| Predicate | timeDivisionMyth |
P189836
|
FINISHED |
| Object | spends six months in the forest |
—
|
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: spends six months in the forest | Statement: [Logun Ede, timeDivisionMyth, spends six months in the forest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeDivisionMyth Context triple: [Logun Ede, timeDivisionMyth, spends six months in the forest]
-
A.
timeInMyth
Indicates that an entity exists or occurs during a specific time period within a mythological narrative or tradition.
-
B.
timeDomain
Indicates that something is characterized, defined, or analyzed with respect to time rather than another domain (such as frequency or space).
-
C.
timeCycle
Indicates a recurring temporal pattern or interval in which an event, state, or process regularly repeats.
-
D.
timescale
Indicates the temporal scale or duration over which a process, relationship, or effect occurs or is evaluated.
-
E.
timeExistence
Indicates the period or duration during which an entity exists or is valid.
- F. None of above. chosen
Provenance (4 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_69f76efa37088190be5416b7ef1ca275 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbca6c066c8190a1599202f341417f |
completed | May 6, 2026, 11:10 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
| PDg | Predicate description generation | batch_69fbc993caa881908c16c3e21efaeef9 |
completed | May 6, 2026, 11:07 p.m. |
Created at: May 3, 2026, 4:20 p.m.