Triple
T5737196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dharma |
E126529
|
entity |
| Predicate | roleInIndividualLife |
P65533
|
FINISHED |
| Object | guides personal conduct |
—
|
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: guides personal conduct | Statement: [Dharma, roleInIndividualLife, guides personal conduct]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInIndividualLife Context triple: [Dharma, roleInIndividualLife, guides personal conduct]
-
A.
positionOnHumanLife
Indicates a stance or viewpoint that an entity holds regarding the value, rights, or treatment of human life.
-
B.
roleInIndustry
Indicates the specific function, position, or capacity an entity holds within a particular industry or sector.
-
C.
roleInCommunity
Indicates the function, position, or set of responsibilities an entity holds within a particular community or group.
-
D.
hasPersonalLife
Indicates that an entity has aspects, activities, or relationships belonging to its private or non-professional life.
-
E.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
- 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_69c0083082288190b7478cead6b5430a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0255ad6f48190977bf4f037110aa3 |
completed | March 22, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69c021c8195481909419808b002628aa |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c022a50c048190aff24c63e7039dd6 |
completed | March 22, 2026, 5:11 p.m. |
Created at: March 22, 2026, 3:47 p.m.