Triple
T10893525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salem Lights |
E257244
|
entity |
| Predicate | hasPerceivedAttribute |
P78428
|
FINISHED |
| Object | milder taste compared to regular Salem |
—
|
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: milder taste compared to regular Salem | Statement: [Salem Lights, hasPerceivedAttribute, milder taste compared to regular Salem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerceivedAttribute Context triple: [Salem Lights, hasPerceivedAttribute, milder taste compared to regular Salem]
-
A.
hasPerception
Indicates that one entity is aware of, senses, or recognizes another entity or phenomenon.
-
B.
perceivedAttribute
chosen
Indicates that one entity recognizes, interprets, or assigns a particular attribute or quality to another entity.
-
C.
hasFanPerception
Indicates that an entity is perceived, interpreted, or regarded in a particular way by its fans or fan community.
-
D.
hasPublicPerception
Indicates that an entity is associated with a particular way it is viewed, judged, or regarded by the general public or society.
-
E.
perceptionBySelf
Indicates that an entity has a perception, awareness, or sensory experience of itself.
- 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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d75d0089e48190be7a971c2d4f42c2 |
completed | April 9, 2026, 8:02 a.m. |
| PD | Predicate disambiguation | batch_69d70d3943c881908895397eccc3e415 |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:21 p.m.