Triple
T29492340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Divya Saasha |
E748113
|
entity |
| Predicate | knownForAvoiding |
P92600
|
FINISHED |
| Object | public spotlight |
—
|
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: public spotlight | Statement: [Divya Saasha, knownForAvoiding, public spotlight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownForAvoiding Context triple: [Divya Saasha, knownForAvoiding, public spotlight]
-
A.
seeksToAvoid
chosen
Indicates an entity’s intention or effort to stay away from, prevent, or not experience another entity or situation.
-
B.
avoidedFor
Indicates that one entity is deliberately not used, chosen, or engaged with because of the presence, influence, or characteristics of another entity.
-
C.
designedToAvoid
Indicates that something was intentionally created or configured in a way that prevents or minimizes a particular outcome, condition, or interaction.
-
D.
mustAvoid
Indicates that one entity is required to stay away from, not engage with, or prevent interaction with another entity or condition.
-
E.
designedToBeAvoided
Indicates that something is intentionally created or arranged in a way that people should avoid using, encountering, or engaging with it.
- 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_69f0bd448c6881908aa6b475cefd5ddc |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 28, 2026, 4:15 p.m.