Triple
T3753828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Syene |
E81995
|
entity |
| Predicate | presentDayPartOf |
P3475
|
FINISHED |
| Object | city of Aswan |
—
|
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: city of Aswan | Statement: [Syene, presentDayPartOf, city of Aswan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentDayPartOf Context triple: [Syene, presentDayPartOf, city of Aswan]
-
A.
partOfPresentDay
chosen
Indicates that one entity is a component, region, or subset of what constitutes the other entity in its current, modern-day form.
-
B.
presentDayControl
Indicates that one entity currently holds authority, governance, or control over another entity in the present day.
-
C.
presentDayCenter
Indicates that an entity currently serves as the central or primary focal point (e.g., administrative, cultural, or functional center) of another entity in the present day.
-
D.
presentDayDepartment
Indicates that an entity is currently administered or located within a specific modern-day department (administrative division).
-
E.
presentDayDistrict
Indicates that one administrative district corresponds to or is located within the boundaries of a specified present-day district.
- 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_69ad8b1db40081908b61ffa6b78afd4d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb9340e0819083215989718b4598 |
completed | March 8, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69adc04adebc819088d7f36d0ac343a6 |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:35 p.m.