Triple
T1083417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian philosophical texts (Darśanas) |
E23997
|
entity |
| Predicate | employConcept |
P531
|
FINISHED |
| Object | dharma |
—
|
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: dharma | Statement: [Indian philosophical texts (Darśanas), employConcept, dharma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: employConcept Context triple: [Indian philosophical texts (Darśanas), employConcept, dharma]
-
A.
employedPeople
Indicates that there exists a relationship where people are currently working in jobs or positions, typically under an employer.
-
B.
employsForm
Indicates that an entity makes use of or applies a particular form or format in carrying out an action or function.
-
C.
worksFor
Indicates that one entity is employed by or performs work on behalf of another entity, typically an organization or individual.
-
D.
hasConcept
chosen
Indicates that an entity includes, embodies, or is associated with a particular concept.
-
E.
usedInWork
Indicates that something (such as a concept, method, material, or component) is employed or applied within a particular work, project, or creation.
- 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_69a493f1ddf48190a99d54b00e99f8ce |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b95e56948190a1e92367ad7240b7 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b73f4310819086281f8ec67d1a32 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.