Triple
T34539122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maakherure |
E886754
|
entity |
| Predicate | timeOfUseApproximateEnd |
P35259
|
FINISHED |
| Object | c. 1790 BC |
—
|
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: c. 1790 BC | Statement: [Maakherure, timeOfUseApproximateEnd, c. 1790 BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfUseApproximateEnd Context triple: [Maakherure, timeOfUseApproximateEnd, c. 1790 BC]
-
A.
timePeriodEndApprox
chosen
Indicates that the associated time period ends at an approximate, rather than exact, point in time.
-
B.
typicallyEndsAt
Indicates that an event, process, or activity most commonly or usually concludes at a particular time, place, or state.
-
C.
periodInPowerEnd
Indicates the point in time when an entity’s tenure or period in power comes to an end.
-
D.
timeOfSettingEnd
Indicates the point in time at which a specified setting, condition, or configuration ceases to be in effect.
-
E.
typicalEndHourLocal
Indicates the usual local-time clock hour at which an activity, event, or operation typically ends.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
Created at: May 1, 2026, 2:02 a.m.