Triple
T10742753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jain monks |
E253367
|
entity |
| Predicate | idealState |
P17030
|
FINISHED |
| Object | complete detachment |
—
|
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: complete detachment | Statement: [Jain monks, idealState, complete detachment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: idealState Context triple: [Jain monks, idealState, complete detachment]
-
A.
hasIdeal
Indicates that an entity holds or is associated with a guiding principle, standard, or value it considers perfect or most desirable.
-
B.
coreIdeal
chosen
Indicates that something is a fundamental, central principle or value that defines or strongly guides another entity.
-
C.
ultimateState
Indicates the final or end condition that an entity or process ultimately reaches after all preceding stages or transitions.
-
D.
standardState
Indicates that an entity is in its default, reference, or officially recognized condition or configuration under standard conditions.
-
E.
principalState
Indicates that an entity serves as the primary or main state associated with another entity or context.
- 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d711b5dd8c81908f1d9b126e4c3ae7 |
completed | April 9, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69d6f30df9948190ab3cdc33977fac14 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:15 p.m.