Triple
T30303362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amonasro |
E770708
|
entity |
| Predicate | relationshipToAmneris |
P203870
|
FINISHED |
| Object | political enemy of Amneris’s people |
—
|
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: political enemy of Amneris’s people | Statement: [Amonasro, relationshipToAmneris, political enemy of Amneris’s people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToAmneris Context triple: [Amonasro, relationshipToAmneris, political enemy of Amneris’s people]
-
A.
relationshipToRadamès
Indicates the specific type of personal or social relationship an entity has with Radamès.
-
B.
associatedWithPharaoh
Indicates a relationship in which an entity has a connection, link, or involvement with a pharaoh, such as through service, rule, influence, or historical association.
-
C.
relationshipToAmina
Indicates the specific type of relationship or connection that an entity has with Amina.
-
D.
marriedToPharaoh
Indicates that one entity is the spouse of a pharaoh in a marital relationship.
-
E.
motherOfPharaoh
Indicates that one entity is the mother (biological or adoptive) of another entity who holds the title or role of pharaoh.
- F. None of above. chosen
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_69f224881b948190b8c4921b250a44a3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a022c5269888190944314074aedfe73 |
completed | May 11, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_6a02286020308190b238183f7ba2065f |
completed | May 11, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a022c51bd5c81909e9bf265bf39cd24 |
completed | May 11, 2026, 7:21 p.m. |
Created at: April 29, 2026, 7:49 p.m.