Triple
T2962095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tigrinya Muslims |
E80071
|
entity |
| Predicate | commonBeverage |
P4038
|
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: [Tigrinya Muslims, commonBeverage, coffee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonBeverage Context triple: [Tigrinya Muslims, commonBeverage, coffee]
-
A.
typicalCaffeineSource
Indicates that one entity is a common or characteristic source from which the other entity typically obtains caffeine.
-
B.
featuresBeverage
Indicates that one entity includes, offers, or presents a particular beverage as part of its contents, services, or characteristics.
-
C.
drinks
Indicates that one entity consumes a liquid substance, typically by ingesting it through the mouth.
-
D.
traditionalDrink
chosen
Indicates that one entity is a beverage customarily consumed within the culture, heritage, or longstanding practices associated with another entity.
-
E.
hasCaffeineContent
Indicates that one entity (typically a beverage or substance) possesses a specified amount or presence of caffeine.
- 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_69ad8b1341848190bd19dbf46892887d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9955e6488190bea170724d5fbfe8 |
completed | March 8, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69ad960c5c8881909d679912bd7d78f3 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:57 p.m.