Triple
T17791310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tel Qeiyafa |
E444167
|
entity |
| Predicate | estimatedDateOfAbandonment |
P49984
|
FINISHED |
| Object | early 10th 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: early 10th century BCE | Statement: [Tel Qeiyafa, estimatedDateOfAbandonment, early 10th century BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedDateOfAbandonment Context triple: [Tel Qeiyafa, estimatedDateOfAbandonment, early 10th century BCE]
-
A.
dateOfAbandonment
chosen
Indicates the specific date on which something (such as a place, project, or object) was formally or effectively abandoned or discontinued.
-
B.
periodOfAbandonment
Indicates a time span during which something is left unused, unattended, or not maintained.
-
C.
decayDate
Indicates the date on which something ceases to be valid, effective, or usable (i.e., when it expires or decays).
-
D.
decommissioningStartDate
Indicates the date on which the process of taking an asset or system out of active service is initiated.
-
E.
decommissioningEndDate
Indicates the date on which a decommissioning process or status for something is completed or officially ends.
- 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_69d8b9efe370819095cd219b143ae727 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48797408081908c48d98e1525ae87 |
completed | April 19, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:13 a.m.