Triple
T34537466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | el-Ashmunein |
E886707
|
entity |
| Predicate | modernSettlementOverlies |
P128342
|
FINISHED |
| Object | ruins of Hermopolis |
—
|
NE NERFINISHED |
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: ruins of Hermopolis | Statement: [el-Ashmunein, modernSettlementOverlies, ruins of Hermopolis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernSettlementOverlies Context triple: [el-Ashmunein, modernSettlementOverlies, ruins of Hermopolis]
-
A.
modernSettlementArea
Indicates the geographic area occupied by a settlement in its modern or current form.
-
B.
hasHumanSettlement
Indicates that a location or area contains or is the site of a human settlement, such as a town, village, or city.
-
C.
modernSettlement
chosen
Indicates that the subject is a contemporary or currently existing human settlement located at the object.
-
D.
mainSettlementLocatedOn
Indicates that the primary settlement of an area is situated on or directly adjacent to a specified geographic feature or location.
-
E.
mainSettlement
Indicates that one settlement serves as the primary or most important settlement associated with a given area, region, or administrative unit.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: May 1, 2026, 2:02 a.m.