Triple
T30032913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mundhum |
E763071
|
entity |
| Predicate | hasSpecialistPractitioner |
P39849
|
FINISHED |
| Object | Phedangma |
—
|
NE NERFINISHED |
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: Phedangma | Statement: [Mundhum, hasSpecialistPractitioner, Phedangma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpecialistPractitioner Context triple: [Mundhum, hasSpecialistPractitioner, Phedangma]
-
A.
hasSpecialist
chosen
Indicates that one entity is associated with or assigned to a specialist entity that provides expert support, service, or oversight for it.
-
B.
hasSpecialistStatus
Indicates that an entity holds a recognized specialist designation or status in a particular field, role, or context.
-
C.
hasSpecialty
Indicates that an entity possesses a particular area of expertise, focus, or professional specialization.
-
D.
practitionerType
Indicates the specific category or role of practitioner associated with an entity (e.g., doctor, nurse, therapist).
-
E.
hasSpecialistLists
Indicates that an entity maintains or is associated with one or more curated lists of specialists or specialized items.
- 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_69f2246fb2b88190acff36bf7975c8f0 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: April 29, 2026, 6:50 p.m.