Triple
T26385901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sherie Rene Scott as Amneris |
E663278
|
entity |
| Predicate | portraysRelationshipWith |
P174335
|
FINISHED |
| Object | Aida |
—
|
NE NERFINISHED |
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: Aida | Statement: [Sherie Rene Scott as Amneris, portraysRelationshipWith, Aida]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portraysRelationshipWith Context triple: [Sherie Rene Scott as Amneris, portraysRelationshipWith, Aida]
-
A.
portraysRelationship
Indicates that one entity depicts, represents, or illustrates a relationship between other entities.
-
B.
portraysRelation
Indicates that one entity depicts, represents, or acts in the role of another entity within some medium or context.
-
C.
portraysCharacterRelationship
Indicates that one entity depicts or represents the relationship between characters in another entity.
-
D.
showsRelationshipWith
Indicates that one entity visually or explicitly presents or demonstrates its connection or association with another entity.
-
E.
inRelationshipWith
Indicates that two entities are mutually involved in a defined personal, romantic, or partnership relationship with each other.
- 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6c20f209081909fb9ac8f95069f04 |
completed | May 3, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c125695c81909704c67bef4ce5b2 |
completed | May 3, 2026, 3:29 a.m. |
Created at: April 26, 2026, 11:22 p.m.