Triple
T19529348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dangun myth |
E488617
|
entity |
| Predicate | timeOfFoundationDescribed |
P41
|
FINISHED |
| Object | 2333 BCE |
—
|
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: 2333 BCE | Statement: [Dangun myth, timeOfFoundationDescribed, 2333 BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfFoundationDescribed Context triple: [Dangun myth, timeOfFoundationDescribed, 2333 BCE]
-
A.
foundingAround
Indicates that an entity was founded at approximately, but not exactly, the specified time or within a loosely defined surrounding period.
-
B.
foundedBefore
Indicates that one entity was established or created at an earlier time than the other entity.
-
C.
portrayedAsFoundedIn
Indicates that an entity is depicted or represented as having been founded in a particular time or place, regardless of historical accuracy.
-
D.
describesFoundingOf
Indicates that one entity specifies or provides details about the establishment or creation (founding) of another entity.
-
E.
foundedOn
chosen
Indicates that an entity was established, created, or brought into existence on a specific date or point in time.
- 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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6363dfd6c8190aaa0b374184965bb |
completed | April 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69e514c9c00481909b76bda67957e58b |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:41 p.m.