Triple
T30169033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kassites |
E766867
|
entity |
| Predicate | approximateRuleEnd |
P8204
|
FINISHED |
| Object | c. 12th 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. 12th century BCE | Statement: [Kassites, approximateRuleEnd, c. 12th century BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateRuleEnd Context triple: [Kassites, approximateRuleEnd, c. 12th century BCE]
-
A.
typicalEndRule
Indicates the rule or condition that normally determines how or when a process, event, or relationship comes to an end.
-
B.
hasApproximateEnd
chosen
Indicates that an entity’s end point, time, or boundary is known only approximately rather than precisely.
-
C.
endRule
Indicates that a previously active rule, regulation, or governing condition is terminated or ceases to apply.
-
D.
hasEndingCountApproximate
Indicates that the number of endings associated with an entity is known only approximately rather than as an exact count.
-
E.
reasonForEndOfRule
Indicates the cause, circumstance, or event that led to the termination or conclusion of a particular rule or period of rule.
- 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_69fdbaa226708190b8ed96e93aad38de |
completed | May 8, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69fdb58b07e48190837e00966de050d4 |
completed | May 8, 2026, 10:06 a.m. |
Created at: April 29, 2026, 7:24 p.m.