Triple
T34020721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aryika |
E872371
|
entity |
| Predicate | expectedConduct |
P76459
|
FINISHED |
| Object | strict ethical purity |
—
|
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: strict ethical purity | Statement: [Aryika, expectedConduct, strict ethical purity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expectedConduct Context triple: [Aryika, expectedConduct, strict ethical purity]
-
A.
expectedAction
Indicates that a particular action is anticipated or required to occur in a given context or scenario.
-
B.
conducts
Indicates that an entity organizes, directs, or carries out an activity, operation, or process involving another entity.
-
C.
concernsTypeOfConduct
chosen
Indicates that something is about or relates specifically to a particular type or category of conduct or behavior.
-
D.
advisedBehavior
Indicates that one entity recommends or counsels a particular behavior or course of action to another entity.
-
E.
expectedDuty
Indicates that one entity is obligated or anticipated to perform a particular duty or responsibility toward another entity or within a given 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_69f349a19ad88190ab586f010c804a8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:51 a.m.