Triple
T33184933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Candy |
E849439
|
entity |
| Predicate | hasInformalConnotation |
P4340
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Candy, hasInformalConnotation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInformalConnotation Context triple: [Candy, hasInformalConnotation, yes]
-
A.
hasInformalUsage
Indicates that something is used in casual or non-standard contexts rather than in formal or official usage.
-
B.
hasConnotation
chosen
Indicates that one entity carries an implied or associated meaning, tone, or emotional nuance in relation to another entity.
-
C.
hasNegativeConnotation
Indicates that the referenced term, expression, or association carries an unfavorable, disapproving, or undesirable implication.
-
D.
hasPositiveConnotation
Indicates that something is associated with favorable, pleasant, or approving meanings, feelings, or implications.
-
E.
usedInformallyAlongside
Indicates that something is employed in an informal, non-standard way together with or in addition to something else.
- 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_69f3495e0f108190a6a7006f79f9c2c3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ffcf46fd688190907fd1ceb499a8d1 |
completed | May 10, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69ffccde2a8c81908e055e74077dbd19 |
completed | May 10, 2026, 12:10 a.m. |
Created at: May 1, 2026, 1:29 a.m.