Triple
T16211321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Double Shot |
E393471
|
entity |
| Predicate | experienceIntensity |
P99309
|
FINISHED |
| Object | intense |
—
|
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: intense | Statement: [Double Shot, experienceIntensity, intense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: experienceIntensity Context triple: [Double Shot, experienceIntensity, intense]
-
A.
experienceDuration
Indicates the length of time over which an entity undergoes or has undergone a particular experience or event.
-
B.
experienceStyle
Indicates that one entity has or is associated with a particular manner, approach, or style in which an experience is delivered or undergone.
-
C.
difficulty
Indicates the level of challenge, complexity, or effort required to perform an action, solve a problem, or achieve a particular outcome.
-
D.
eraOfIncreasedIntensity
Indicates a period during which the level or strength of a particular activity, condition, or phenomenon becomes significantly higher than before.
-
E.
exposureLevel
chosen
Indicates the degree or intensity to which an entity is subjected or exposed to a particular factor, condition, or influence.
- 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e227f1bef8819094e724f5cd0b86d5 |
completed | April 17, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.