Triple
T14820945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tell el-Ful |
E348447
|
entity |
| Predicate | modernStructureStatus |
P38811
|
FINISHED |
| Object | abandoned |
—
|
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: abandoned | Statement: [Tell el-Ful, modernStructureStatus, abandoned]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernStructureStatus Context triple: [Tell el-Ful, modernStructureStatus, abandoned]
-
A.
modernStatus
Indicates the current or contemporary condition, classification, or standing of an entity in the present time.
-
B.
currentStructure
Indicates that an entity is the present or active structural configuration or organization associated with another entity.
-
C.
actualStatus
Indicates the current, real-world state or condition of an entity, as opposed to a planned, expected, or nominal status.
-
D.
hasBuildingStatus
chosen
Indicates the current condition, classification, or operational state assigned to a building.
-
E.
maintenanceStatus
Indicates the current state or condition of an entity with respect to its maintenance activities, such as whether it is pending, in progress, completed, or overdue.
- 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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decfe64328819083ce42704cf0602d |
completed | April 14, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69de8c0ef8a4819092d84478b1f56db1 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:50 a.m.