Triple
T25283347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pushya |
E633872
|
entity |
| Predicate | avoidedFor |
P158336
|
FINISHED |
| Object | Marriage in some traditions |
—
|
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: Marriage in some traditions | Statement: [Pushya, avoidedFor, Marriage in some traditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: avoidedFor Context triple: [Pushya, avoidedFor, Marriage in some traditions]
-
A.
seeksToAvoid
Indicates an entity’s intention or effort to stay away from, prevent, or not experience another entity or situation.
-
B.
avoidedConsequence
Indicates that an action or event prevented a particular consequence from occurring.
-
C.
designedToAvoid
Indicates that something was intentionally created or configured in a way that prevents or minimizes a particular outcome, condition, or interaction.
-
D.
triedToAvoid
Indicates an entity made an effort or took action to prevent contact with, involvement in, or the occurrence of another entity or situation.
-
E.
mustAvoid
Indicates that one entity is required to stay away from, not engage with, or prevent interaction with another entity or condition.
- 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_69e75a9402fc81909362ca85277c06d9 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48e0718908190a2ebc862db79e2ea |
completed | May 1, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
| PDg | Predicate description generation | batch_69f465699c9c8190ac7b4b32b782550c |
completed | May 1, 2026, 8:33 a.m. |
Created at: April 21, 2026, 1:19 p.m.