Triple
T11868876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jains |
E282354
|
entity |
| Predicate | layIdeal |
P69857
|
FINISHED |
| Object | observance of small vows (anuvratas) |
—
|
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: observance of small vows (anuvratas) | Statement: [Jains, layIdeal, observance of small vows (anuvratas)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: layIdeal Context triple: [Jains, layIdeal, observance of small vows (anuvratas)]
-
A.
lays
Indicates that one entity deposits or places something, typically eggs or objects, onto a surface or in a location.
-
B.
hasIdeal
chosen
Indicates that an entity holds or is associated with a guiding principle, standard, or value it considers perfect or most desirable.
-
C.
coreIdeal
Indicates that something is a fundamental, central principle or value that defines or strongly guides another entity.
-
D.
liesBelow
Indicates that one entity is positioned at a lower vertical level than another entity.
-
E.
hasIdealization
Indicates that one entity is a simplified, abstracted, or ideal form or model of another entity, capturing its essential features while omitting complexities.
- 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_69d6ab2945d081908a5851c916cbcfb5 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a73c04e4819084c0b2ff8e5d2f04 |
completed | April 10, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_69d8a2589f0c8190ad82ff11acabae93 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.