Triple
T36471933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | workshop of Thutmose |
E898558
|
entity |
| Predicate | locatedInArchaeologicalZone |
P167717
|
FINISHED |
| Object | Tell el-Amarna |
E376823
|
NE 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: Tell el-Amarna | Statement: [workshop of Thutmose, locatedInArchaeologicalZone, Tell el-Amarna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInArchaeologicalZone Context triple: [workshop of Thutmose, locatedInArchaeologicalZone, Tell el-Amarna]
-
A.
belongsToArchaeologicalZone
chosen
Indicates that something is part of, contained within, or officially assigned to a specific archaeological zone or site.
-
B.
foundInArchaeologicalZoneCategory
Indicates that an entity is located within or associated with a specific category of archaeological zone.
-
C.
hasArchaeologicalSiteIn
Indicates that an entity possesses, contains, or is associated with an archaeological site located within a specified place or region.
-
D.
locatedInHistoricSite
Indicates that an entity is situated within or on the grounds of a place officially recognized as a historic site.
-
E.
hasNearbyArchaeologicalSite
Indicates that an entity is located close to or in the vicinity of an archaeological site.
- F. None of above.
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_69f76e58ebd88190b75d9b169b59d793 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39e6d0cfd08190a1d959c3eac0df2a |
completed | June 23, 2026, 1:52 a.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.