Triple
T34537463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | el-Ashmunein |
E886707
|
entity |
| Predicate | hasMaterialCultureFrom |
P1439
|
FINISHED |
| Object | New Kingdom |
E47125
|
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: New Kingdom | Statement: [el-Ashmunein, hasMaterialCultureFrom, New Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaterialCultureFrom Context triple: [el-Ashmunein, hasMaterialCultureFrom, New Kingdom]
-
A.
hasCulturalObject
Indicates that one entity possesses, contains, or is associated with a cultural object (such as an artwork, artifact, or culturally significant item).
-
B.
hasCulturalProduct
Indicates that an entity possesses, produces, or is associated with a cultural artifact, work, or output (such as art, literature, music, or media).
-
C.
hasArchaeologicalMaterial
Indicates that an entity possesses, contains, or is associated with specific archaeological materials or artifacts.
-
D.
hasAssociatedCulture
chosen
Indicates that an entity is related to, influenced by, or characterized by a particular culture.
-
E.
hasCulturalProperty
Indicates that something possesses or is associated with a cultural attribute, value, or characteristic.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a01ade363088190b3a3e3dedabd1aa2 |
completed | May 11, 2026, 10:22 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3740ee9c688190bc1f936bf4410d79 |
completed | June 21, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_6a01acf3c5788190932bd8fcf27c123d |
completed | May 11, 2026, 10:18 a.m. |
Created at: May 1, 2026, 2:02 a.m.