Triple
T29836077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pitta dosha |
E757660
|
entity |
| Predicate | primaryLocationInBody |
P21283
|
FINISHED |
| Object | small intestine |
—
|
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: small intestine | Statement: [Pitta dosha, primaryLocationInBody, small intestine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryLocationInBody Context triple: [Pitta dosha, primaryLocationInBody, small intestine]
-
A.
seatOfBody
Indicates that one entity serves as the physical location or base where another entity (typically an organization or authority) is situated or headquartered.
-
B.
locatedOnBody
Indicates that one entity is physically situated on the surface or external part of another entity’s body.
-
C.
hasBodyRegion
chosen
Indicates that an entity possesses, includes, or is associated with a specific anatomical or bodily region.
-
D.
isProminentPartOf
Indicates that something forms a major, highly noticeable, or significant component of a larger whole.
-
E.
discoveredOnBody
Indicates that something (such as an item, mark, or substance) was found on the surface or person of a body.
- 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_69f224593f6c81908785a560fe659f58 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a019579463c8190b51e39183b57bbaf |
completed | May 11, 2026, 8:38 a.m. |
| PD | Predicate disambiguation | batch_6a0192d309488190a3d86c93e7138c77 |
completed | May 11, 2026, 8:26 a.m. |
Created at: April 29, 2026, 5:37 p.m.