Triple
T30169032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kassites |
E766867
|
entity |
| Predicate | approximateRuleStart |
P120141
|
FINISHED |
| Object | c. 16th 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. 16th century BCE | Statement: [Kassites, approximateRuleStart, c. 16th century BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateRuleStart Context triple: [Kassites, approximateRuleStart, c. 16th century BCE]
-
A.
startOfRule
Indicates that one element marks the beginning boundary or initial segment of a specified rule.
-
B.
beganRule
Indicates that an entity started its period of ruling or governance over another entity or domain.
-
C.
startRule
Indicates that a particular rule is the initial or entry rule from which a process, system, or evaluation begins.
-
D.
coRuleStart
Indicates the point in time or sequence at which two or more rules begin to apply or take effect together.
-
E.
regulationStartApprox
chosen
Indicates that the start of a regulation or regulatory period is known only approximately rather than as an exact date or 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdb45537288190b6791078d4a6899f |
completed | May 8, 2026, 10 a.m. |
| PD | Predicate disambiguation | batch_69fdb39ad96481908376d7def9fafc13 |
completed | May 8, 2026, 9:57 a.m. |
Created at: April 29, 2026, 7:24 p.m.