Triple
T18515365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ἥβη |
E452446
|
entity |
| Predicate | servedDrink |
P131968
|
FINISHED |
| Object | nectar |
—
|
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: nectar | Statement: [Ἥβη, servedDrink, nectar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedDrink Context triple: [Ἥβη, servedDrink, nectar]
-
A.
beverageBase
Indicates that one entity serves as the primary liquid or foundational ingredient used to make a beverage involving the other entity.
-
B.
servedWithIce
Indicates that one item is provided or presented accompanied by ice.
-
C.
drinks
Indicates that one entity consumes a liquid substance, typically by ingesting it through the mouth.
-
D.
traditionalDrink
Indicates that one entity is a beverage customarily consumed within the culture, heritage, or longstanding practices associated with another entity.
-
E.
hasBeverageReference
Indicates that one entity makes reference to, mentions, or is associated with a beverage in some way.
- 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53349415c8190b989b536e2d1c40a |
completed | April 19, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69e469e0025c81908f16ed4f922674af |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2b93bc8190a6070018d7046547 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:36 a.m.