Triple
T2102168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epic of Gilgamesh |
E37113
|
entity |
| Predicate | standardVersionDate |
P33818
|
FINISHED |
| Object | first millennium 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: first millennium BCE | Statement: [Epic of Gilgamesh, standardVersionDate, first millennium BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardVersionDate Context triple: [Epic of Gilgamesh, standardVersionDate, first millennium BCE]
-
A.
officialVersionSince
Indicates the point in time from which a particular version of something is recognized or treated as the official version.
-
B.
preliminaryVersionDate
Indicates the date on which an initial or draft version of something was created, issued, or became available.
-
C.
majorRevisionDate
Indicates the date on which an entity underwent a significant or substantial update or revision.
-
D.
standardizedSince
chosen
Indicates that something has been formally standardized starting from a specific point in time.
-
E.
principalVersionFor
Indicates a relationship where one version of an entity is designated as the primary or authoritative version for another related entity.
- 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_69a8861828948190924aa30c08806b3a |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abbabc83a8819091f786f21d33b5a6 |
completed | March 7, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69abb7b7b6288190afa11b4d93bd5666 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.