Triple
T20342865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pancha Tattva |
E495783
|
entity |
| Predicate | memberRole_2 |
P11687
|
FINISHED |
| Object | Nityananda Prabhu as first expansion of the Lord |
—
|
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: Nityananda Prabhu as first expansion of the Lord | Statement: [Pancha Tattva, memberRole_2, Nityananda Prabhu as first expansion of the Lord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberRole_2 Context triple: [Pancha Tattva, memberRole_2, Nityananda Prabhu as first expansion of the Lord]
-
A.
managementRole
Indicates that one entity holds a managerial or supervisory role with authority and responsibility over another entity.
-
B.
servesRole
chosen
Indicates that one entity performs, fulfills, or occupies a particular function, position, or responsibility in relation to another entity.
-
C.
libraryRole
Indicates the specific function, responsibility, or position an entity holds within the context of a library.
-
D.
unitRole
Indicates the functional role or purpose that a unit serves within a larger system or context.
-
E.
roleInClub
Indicates that an entity holds a specific position or function within a particular club.
- 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_69e0b4a3320881909495ae8bc30bc2dc |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67836b72081908be65115abdb37bf |
completed | April 20, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69e57636b4808190bc2855af48a3ccdc |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:24 a.m.