Triple
T9100229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscow maternity hospitals |
E218131
|
entity |
| Predicate | typicalStaff |
P478
|
FINISHED |
| Object | obstetrician-gynecologists |
—
|
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: obstetrician-gynecologists | Statement: [Moscow maternity hospitals, typicalStaff, obstetrician-gynecologists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalStaff Context triple: [Moscow maternity hospitals, typicalStaff, obstetrician-gynecologists]
-
A.
typicalMembers
Indicates that the related entities are representative or characteristic members of a larger group, category, or class.
-
B.
typicalGroup
Indicates that the subject belongs to or represents a standard, characteristic, or commonly occurring group associated with the object.
-
C.
staffIncluded
chosen
Indicates that staff members are included or provided as part of the associated entity, service, or arrangement.
-
D.
personnelType
Indicates the classification or role category assigned to a person within an organization or system.
-
E.
typicalRole
Indicates that one entity serves as the usual, characteristic, or commonly expected role or function of another entity.
- 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_69ca83d9844081908e561e367fda6d45 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc9711babc8190a336812dd08d9c73 |
completed | April 1, 2026, 3:54 a.m. |
| PD | Predicate disambiguation | batch_69cc65fc7f408190a5846e29ab3b97e5 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:15 p.m.