Triple
T8550211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Idli |
E202426
|
entity |
| Predicate | isTypicallyServedFor |
P92845
|
FINISHED |
| Object | breakfast |
—
|
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: breakfast | Statement: [Idli, isTypicallyServedFor, breakfast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTypicallyServedFor Context triple: [Idli, isTypicallyServedFor, breakfast]
-
A.
servesType
Indicates that one entity provides, offers, or is used to deliver a particular type, category, or kind of thing or service.
-
B.
servesMostly
Indicates that one entity primarily functions to serve, support, or cater to another entity, more than to any other.
-
C.
typicallyServedAs
Indicates that something is most commonly presented, used, or offered in a particular role, form, or function.
-
D.
intendedToServe
Indicates that one entity was designed, planned, or purposed specifically to benefit, assist, or fulfill the needs of another entity.
-
E.
alsoServes
Indicates that an entity, in addition to its primary role or function, provides service or support to another specified entity or group.
- 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_69ca832610e08190b3b6c6cd2c250255 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe75589d8819096177ddbd3dafcb6 |
completed | March 31, 2026, 3:25 p.m. |
| PD | Predicate disambiguation | batch_69cbd113e05c81908f4f3fc1b5925164 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69d4c7c15c708190997122e3e472734f |
completed | April 7, 2026, 9 a.m. |
Created at: March 30, 2026, 6:19 p.m.