Triple
T31882089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Level III (Assyrian destruction level) |
E813908
|
entity |
| Predicate | destructionApproximateYear |
P11807
|
FINISHED |
| Object | 701 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: 701 BCE | Statement: [Level III (Assyrian destruction level), destructionApproximateYear, 701 BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: destructionApproximateYear Context triple: [Level III (Assyrian destruction level), destructionApproximateYear, 701 BCE]
-
A.
demolitionYearApprox
Indicates that an entity was demolished in or around a particular year, where the year is an approximate rather than an exact value.
-
B.
destructionYear
chosen
Indicates the year in which an entity was destroyed or ceased to exist due to destructive events or actions.
-
C.
demolitionDecisionYear
Indicates the year in which a formal decision was made to demolish something.
-
D.
estimatedYearOfCreation
Indicates the year in which something is believed or approximated to have been created, rather than a precisely known creation year.
-
E.
reconstructionOrRestorationDate
Indicates the date on which an entity was reconstructed or restored after damage, alteration, or deterioration.
- 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_69f348ed74bc81909846aaa6a3c7318c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b21e7e088190832a3db585daea1c |
completed | May 3, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 30, 2026, 11:56 p.m.