Triple
T33585481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kheperkara |
E860266
|
entity |
| Predicate | timeOfUseApproximate |
P125927
|
FINISHED |
| Object | c. 20th century 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: c. 20th century BCE | Statement: [Kheperkara, timeOfUseApproximate, c. 20th century BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfUseApproximate Context triple: [Kheperkara, timeOfUseApproximate, c. 20th century BCE]
-
A.
recommendedUsageTime
Indicates the period of time for which something is advised or intended to be used.
-
B.
hasOffPeakUsage
Indicates that an entity exhibits or is associated with usage occurring during designated off-peak times rather than standard peak periods.
-
C.
hasTypicalUseTime
Indicates the usual or expected duration or time period during which something is commonly used or in operation.
-
D.
endTimeApproximate
Indicates that the recorded end time of an event or action is not exact but an approximate value.
-
E.
timeframeApproximate
chosen
Indicates that the time period associated with an event or relation is not exact but only roughly or loosely specified.
- 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_69f3497e70e48190951c94d072879bec |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd3d46d1f48190a1b20dd063224b7d |
completed | May 8, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69fd3ae1510c81908fe1280efc17feee |
completed | May 8, 2026, 1:22 a.m. |
Created at: May 1, 2026, 1:40 a.m.