Triple
T36471972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ÄM 21300 |
E898559
|
entity |
| Predicate | associatedWithSiteOfDiscovery |
P78887
|
FINISHED |
| Object | 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: Amarna | Statement: [ÄM 21300, associatedWithSiteOfDiscovery, Amarna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithSiteOfDiscovery Context triple: [ÄM 21300, associatedWithSiteOfDiscovery, Amarna]
-
A.
associatedFinds
Indicates that one entity is linked to or connected with another entity through related findings, results, or discovered information.
-
B.
discoveredWith
Indicates that one entity was found, detected, or identified using another entity as the means, tool, method, or accompanying context of discovery.
-
C.
relatedToArchaeologicalSite
chosen
Indicates that one entity has a contextual, historical, or functional connection to an archaeological site.
-
D.
discoveredAsFossilSite
Indicates that a location was identified and recognized as a site containing fossils.
-
E.
wasDiscoveredAt
Indicates that an entity was found, identified, or uncovered at a specific place or during a particular event or context.
- 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_6a39f8fcf47c81909c1b927766fdf315 |
completed | June 23, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.