Triple
T29015459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amun cult of Thebes |
E737294
|
entity |
| Predicate | associatedTriad |
P151735
|
FINISHED |
| Object | Theban Triad |
E360522
|
NE 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 Triad | Statement: [Amun cult of Thebes, associatedTriad, Theban Triad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedTriad Context triple: [Amun cult of Thebes, associatedTriad, Theban Triad]
-
A.
associatedWithTrine
chosen
Indicates a relationship in which an entity is connected or linked to a trine, typically signifying involvement, relevance, or contextual association with that trine.
-
B.
triadMemberWith
Indicates a relationship where an entity is a member of a specific triad together with two other associated entities.
-
C.
associatedThrough
Indicates that two entities are connected or related to each other by means of a specified intermediary, context, or linkage.
-
D.
triples
Indicates that one entity performs or achieves something three times or increases another entity to three times its original amount.
-
E.
associatedSin
Indicates a relationship where one entity is linked or connected to a particular sin or wrongful act.
- F. None of above.
Provenance (4 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_6a0249374a8c8190ab19002a123da439 |
completed | May 11, 2026, 9:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2505cdabdc8190818c4b7da541b5e1 |
completed | June 7, 2026, 5:46 a.m. |
| PD | Predicate disambiguation | batch_6a02486194b08190a489ae3a8f4a59a9 |
completed | May 11, 2026, 9:21 p.m. |
Created at: April 28, 2026, 9:45 a.m.