Triple
T28942776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Varaha |
E730494
|
entity |
| Predicate | relatedAvatar |
P57132
|
FINISHED |
| Object | Matsya |
—
|
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: Matsya | Statement: [Varaha, relatedAvatar, Matsya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedAvatar Context triple: [Varaha, relatedAvatar, Matsya]
-
A.
avatar
Indicates that one entity serves as a representation, embodiment, or proxy of another entity, often in a different form or medium.
-
B.
avatarOf
chosen
Indicates that one entity serves as the embodiment, representation, or manifested form of another entity.
-
C.
isLinkedToAvatar
Indicates that one entity is associated or connected to a specific avatar representation of a user or character.
-
D.
associatedWithActorImage
Indicates a relationship where something (such as data, content, or a record) is linked or connected to an actor’s image.
-
E.
relatedIdentity
Indicates that two identities are connected or associated with each other in some meaningful way, such as being alternate, linked, or otherwise contextually related.
- 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_69f043ea0aa88190a25acbf46157995a |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_6a00a22e32f481909b6006c5b1cdefd3 |
completed | May 10, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_6a00a1bd9c908190b4aa17a61f48126f |
completed | May 10, 2026, 3:18 p.m. |
Created at: April 28, 2026, 8:37 a.m.