Triple
T37087905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhat community |
E918338
|
entity |
| Predicate | professionTransmission |
P187123
|
FINISHED |
| Object | hereditary |
—
|
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: hereditary | Statement: [Bhat community, professionTransmission, hereditary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: professionTransmission Context triple: [Bhat community, professionTransmission, hereditary]
-
A.
professionalCategory
Indicates the classification of an entity according to its professional field, role, or occupational domain.
-
B.
professionAttribute
Indicates that a specific attribute, quality, or characteristic is associated with a given profession.
-
C.
professionalOutcome
Indicates the resulting professional status, achievement, or consequence that arises from a person’s work-related actions, experiences, or decisions.
-
D.
professionalSector
Indicates the industry or field in which an entity conducts its professional or occupational activities.
-
E.
professionalBase
Indicates that one entity serves as the primary professional location, organization, or base of operations for another entity.
- 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_69f76e9952b88190a6fe01ba01476520 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb344ba5408190a6fe8face293d88b |
completed | May 6, 2026, 12:30 p.m. |
Created at: May 3, 2026, 4:14 p.m.