Triple
T30624854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vaivasvata Manu |
E779544
|
entity |
| Predicate | avatarAssociation |
P20182
|
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: [Vaivasvata Manu, avatarAssociation, Matsya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: avatarAssociation Context triple: [Vaivasvata Manu, avatarAssociation, Matsya]
-
A.
profileAssociation
Indicates a relationship where one profile is linked, connected, or associated with another profile or related entity.
-
B.
avatar
chosen
Indicates that one entity serves as a representation, embodiment, or proxy of another entity, often in a different form or medium.
-
C.
leaderAssociatedWith
Indicates a relationship where a leader is connected or affiliated with a particular entity, such as an organization, group, or cause.
-
D.
gunaAssociation
Indicates an association or linkage between entities based on shared guna (a particular quality, attribute, or characteristic) that conceptually connects them.
-
E.
originAssociatedWith
Indicates a relationship where an entity is connected to, derived from, or influenced by a particular origin, source, or point of beginning.
- 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_69f224a431548190a44ad9d088dbf91f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a18eee08190b6d3d752e1685177 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:27 p.m.