Triple
T21606289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tꜣ-šmꜥ |
E533180
|
entity |
| Predicate | opposedRegion |
P90333
|
FINISHED |
| Object | northern part of Upper Egypt |
—
|
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: northern part of Upper Egypt | Statement: [tꜣ-šmꜥ, opposedRegion, northern part of Upper Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposedRegion Context triple: [tꜣ-šmꜥ, opposedRegion, northern part of Upper Egypt]
-
A.
opposedDirectionRegion
chosen
Indicates that one region is oriented in the exact opposite direction relative to another region.
-
B.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
C.
opposedPoliticalEntity
Indicates that one political entity is in opposition or conflict with another in terms of policies, ideology, or power.
-
D.
regionOpposedExpansionIn
Indicates that a region actively resisted or opposed the expansion of another entity into its territory or sphere of influence.
-
E.
countryOfOpposition
Indicates the country in which an entity faces opposition, resistance, or adversarial activity.
- 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_69e0c46364608190a337dc8720dc2a35 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef17e5783481909db36c388f3ae227 |
completed | April 27, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69e69665fe8c8190af7e38785db188b2 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:33 p.m.