Triple
T2258277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coffee |
E49777
|
entity |
| Predicate | hasCleanVersion |
P36780
|
FINISHED |
| Object | Coffee |
—
|
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 | Statement: [Coffee, hasCleanVersion, Coffee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCleanVersion Context triple: [Coffee, hasCleanVersion, Coffee]
-
A.
hasVersionIn
Indicates that one entity exists as a specific version or variant within the context, format, or system represented by another entity.
-
B.
hasVersionNumber
Indicates that an entity is associated with a specific version identifier or number.
-
C.
hasNotableVersion
Indicates that an entity has a specific version or variant that is particularly significant, distinguished, or noteworthy compared to other versions.
-
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.
hasVersionToken
Indicates that an entity is associated with a specific version identifier or token that distinguishes one version of it from another.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69abbe86dbcc81908c72793af8fe2a4d |
completed | March 7, 2026, 5:58 a.m. |
Created at: March 4, 2026, 7:48 p.m.