Triple
T33133361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khorsabad |
E847933
|
entity |
| Predicate | abandonedApprox |
P176127
|
FINISHED |
| Object | circa 705 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: circa 705 BCE | Statement: [Khorsabad, abandonedApprox, circa 705 BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abandonedApprox Context triple: [Khorsabad, abandonedApprox, circa 705 BCE]
-
A.
abandonedIn
Indicates that one entity was left behind or deserted in the location or context specified by another entity.
-
B.
abandonedBefore
Indicates that one entity ceased or gave up on something prior in time to another entity doing so.
-
C.
abandonedBy
Indicates that one entity has been deserted, forsaken, or left behind by another entity that was previously present, responsible, or involved.
-
D.
abandonedDuring
Indicates that one entity ceased support for or deserted another entity in the midst of an ongoing process, event, or period.
-
E.
abandonedReason
Indicates the reason or cause for which something was abandoned, discontinued, or given up.
- F. None of above. chosen
Provenance (4 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_69f3495961d88190b16ea542c2c5f825 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6db6a38d881909ecc75cc527910f2 |
completed | May 3, 2026, 5:21 a.m. |
Created at: May 1, 2026, 1:27 a.m.