Triple
T5636250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gezer |
E147955
|
entity |
| Predicate | hasEvidenceOfDestructionLayers |
P32425
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Gezer, hasEvidenceOfDestructionLayers, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEvidenceOfDestructionLayers Context triple: [Gezer, hasEvidenceOfDestructionLayers, yes]
-
A.
hasGeologicalEvidenceOf
Indicates that there is geological data or features supporting the existence, occurrence, or impact of a specified phenomenon or event.
-
B.
hasArchaeologicalLayers
Indicates that one entity contains or exhibits distinct archaeological strata or layers associated with another entity (such as a site, period, or cultural phase).
-
C.
hasArchaeologicalLayer
Indicates that one entity contains, corresponds to, or is associated with a specific archaeological stratigraphic layer within it.
-
D.
hasCauseOfDestruction
Indicates that one entity is the cause or agent responsible for the destruction or damage of another entity.
-
E.
hasArchaeologicalEvidence
chosen
Indicates that there exists archaeological findings or artifacts supporting the existence, occurrence, or characteristics of the related entity or event.
- 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_69c00907bc8881909ed760d3ed73ef35 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c022809f708190ab859aa446683b10 |
completed | March 22, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69c01b1f12ec8190b4b9d9ee31cabe19 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:41 p.m.