Triple
T8994634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radamès |
E214871
|
entity |
| Predicate | loyaltyConflictBetween |
P32882
|
FINISHED |
| Object | love for Aida |
—
|
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: love for Aida | Statement: [Radamès, loyaltyConflictBetween, love for Aida]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loyaltyConflictBetween Context triple: [Radamès, loyaltyConflictBetween, love for Aida]
-
A.
loyaltyConflict
chosen
Indicates a situation where an entity’s loyalties to different people, groups, or principles are in tension or opposition, creating a conflict in choosing whom or what to support.
-
B.
honorsConflict
Indicates that one entity acknowledges and respects an existing conflict or competing obligation involving another entity or situation.
-
C.
conflictedBetween
Indicates being torn or uncertain between two or more options, positions, or commitments.
-
D.
facesConflictWith
Indicates that one entity is in opposition, dispute, or contention with another, involving incompatible goals, interests, or actions.
-
E.
conflictIn
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
- 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_69ca83a05c608190bdfdbdb25e994b39 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc68ddff288190869731df2c178ff6 |
completed | April 1, 2026, 12:37 a.m. |
| PD | Predicate disambiguation | batch_69cc5edba0f88190b97401636a076d7a |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:04 p.m.