Triple
T4063239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I taste a liquor never brewed |
E86263
|
entity |
| Predicate | comparesNatureTo |
P27816
|
FINISHED |
| Object | liquor |
—
|
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: liquor | Statement: [I taste a liquor never brewed, comparesNatureTo, liquor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: comparesNatureTo Context triple: [I taste a liquor never brewed, comparesNatureTo, liquor]
-
A.
hasNature
Indicates that something possesses, exhibits, or is characterized by a particular inherent quality, essence, or fundamental type.
-
B.
sharesNatureWith
chosen
Indicates that two entities possess the same fundamental characteristics, qualities, or essence.
-
C.
viewOnNature
Indicates a person's general attitude, perspective, or philosophy regarding nature and the natural environment.
-
D.
codeNature
Indicates that one entity characterizes or specifies the type, category, or inherent nature of another entity, often in a coded or standardized form.
-
E.
contrastsBiotaWith
Indicates a relationship where one biotic entity or group is explicitly compared to another by highlighting their differences or opposing characteristics.
- 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_69aed93c69208190a4efac0efe3cd69b |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefd0bdea48190805a79515ee92709 |
completed | March 9, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69aef90438908190a005b08ba271eacf |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:38 p.m.