Triple
T15321319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heryshef |
E366296
|
entity |
| Predicate | cultCenterNome |
P114792
|
FINISHED |
| Object | 20th Upper Egyptian nome |
—
|
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: 20th Upper Egyptian nome | Statement: [Heryshef, cultCenterNome, 20th Upper Egyptian nome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cultCenterNome Context triple: [Heryshef, cultCenterNome, 20th Upper Egyptian nome]
-
A.
cultCenterFor
Indicates that a location serves as a primary religious or ritual center dedicated to the worship or veneration of a particular entity.
-
B.
centerOfCultFrom
chosen
Indicates that a location serves as the primary cult center or focal place of worship originating from a particular source or entity.
-
C.
venueComplex
Indicates that one venue is a complex or larger facility that contains or encompasses another venue.
-
D.
centralLocation
Indicates that one entity serves as the primary or central place associated with another entity.
-
E.
sportsFacility
Indicates that one entity is a sports facility where sports or physical activities can take place for the other entity.
- 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_69d85a121520819093dcce999fdefe1a |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03dd460288190b5c41f0a0aeee949 |
completed | April 16, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_69deca9659f48190b8661df223ce5078 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:16 a.m.