Triple
T8974913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kore |
E214361
|
entity |
| Predicate | timeInUnderworld |
P20414
|
FINISHED |
| Object | part of each year |
—
|
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: part of each year | Statement: [Kore, timeInUnderworld, part of each year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeInUnderworld Context triple: [Kore, timeInUnderworld, part of each year]
-
A.
timeInMyth
chosen
Indicates that an entity exists or occurs during a specific time period within a mythological narrative or tradition.
-
B.
timeInTomb
Indicates the duration that an entity remains or has remained inside a tomb.
-
C.
crossToUnderworldBy
Indicates a relationship where an entity travels or passes from the world of the living into the underworld by means of, or with the help of, a specified agent, method, or pathway.
-
D.
timeOfDeath
Indicates the specific time at which an entity (typically a person or organism) died.
-
E.
timeExistence
Indicates the period or duration during which an entity exists or is valid.
- 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_69ca839dbf608190a2f5990477115d29 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6784d1808190899c980f76084ff8 |
completed | April 1, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed9a2d48190ad11381078e823b7 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:02 p.m.