Triple
T2258276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coffee |
E49777
|
entity |
| Predicate | hasExplicitVersion |
P25065
|
FINISHED |
| Object | Coffee (Fucking) |
—
|
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: Coffee (Fucking) | Statement: [Coffee, hasExplicitVersion, Coffee (Fucking)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExplicitVersion Context triple: [Coffee, hasExplicitVersion, Coffee (Fucking)]
-
A.
containsExplicitVersion
chosen
Indicates that one entity includes or specifies a clearly defined, concrete version of another entity.
-
B.
hasVersionNumber
Indicates that an entity is associated with a specific version identifier or number.
-
C.
hasVersionIn
Indicates that one entity exists as a specific version or variant within the context, format, or system represented by another entity.
-
D.
hasSpecialVersion
Indicates that an entity possesses or is associated with a distinct or customized version of another entity, differing from the standard or default form.
-
E.
hasStandardVersion
Indicates that one entity serves as the official or canonical version of another entity.
- 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_69a88aaa9250819095e127d0d77e8a32 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc15839fc8190b17e040c4c765a8c |
completed | March 7, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69abbdb34c148190b51e99f540f97204 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:48 p.m.