Triple
T33093047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | el-Lisht |
E846831
|
entity |
| Predicate | dateOfFlourishing |
P15561
|
FINISHED |
| Object | early 2nd 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: early 2nd millennium BCE | Statement: [el-Lisht, dateOfFlourishing, early 2nd millennium BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfFlourishing Context triple: [el-Lisht, dateOfFlourishing, early 2nd millennium BCE]
-
A.
flourishedDuring
chosen
Indicates that an entity was active, thriving, or at its peak during a specified time period or era.
-
B.
flourishedBetween
Indicates that an entity experienced its period of greatest activity, success, or prominence within a specified time interval.
-
C.
flourishedAfter
Indicates that one entity reached its peak or period of prosperity subsequent to the flourishing or peak period of another entity.
-
D.
flourishedAs
Indicates that an entity thrived, prospered, or reached a peak state in the role, capacity, or form specified by another entity.
-
E.
flourishedBefore
Indicates that one entity reached its peak or period of greatest development earlier in time than another 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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: May 1, 2026, 1:26 a.m.