Triple
T31516569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aneka |
E804086
|
entity |
| Predicate | relationshipTypeWithAyo |
P10690
|
FINISHED |
| Object | romantic partner and co-leader of Midnight Angels |
—
|
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: romantic partner and co-leader of Midnight Angels | Statement: [Aneka, relationshipTypeWithAyo, romantic partner and co-leader of Midnight Angels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipTypeWithAyo Context triple: [Aneka, relationshipTypeWithAyo, romantic partner and co-leader of Midnight Angels]
-
A.
relationshipType
chosen
Indicates the specific kind of relationship that exists between two or more entities.
-
B.
addressesRelationship
Indicates that one entity directs communication, remarks, or attention specifically toward another entity.
-
C.
relationshipTypeStart
Indicates the type or category of relationship that begins or is initiated at a specific point or event.
-
D.
haveRelationshipWith
Indicates that one entity is in some form of defined relationship or association with another entity.
-
E.
relationshipToUser
Indicates the type of connection or association an entity has with the current user.
- 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_69f348ceb0a48190ae7feca263b6296c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 9:53 p.m.