Triple
T29015469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amun cult of Thebes |
E737294
|
entity |
| Predicate | hadPowerBase |
P112282
|
FINISHED |
| Object | Theban priestly aristocracy |
—
|
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: Theban priestly aristocracy | Statement: [Amun cult of Thebes, hadPowerBase, Theban priestly aristocracy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadPowerBase Context triple: [Amun cult of Thebes, hadPowerBase, Theban priestly aristocracy]
-
A.
hasPowerBase
chosen
Indicates that an entity derives support, influence, or authority from a particular group, location, or resource that serves as its primary base of power.
-
B.
hadBase
Indicates that an entity maintained or operated from a particular base location or primary site.
-
C.
hasPower
Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
-
D.
hadPowerType
Indicates that an entity possessed or was associated with a specific type or category of power.
-
E.
hasCorePower
Indicates that an entity possesses a primary or fundamental power, ability, or capability that defines its essential function or role.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f65fe0772881909b1fbc2e28a1206a |
completed | May 2, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:45 a.m.