Triple
T33184255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivan Bezdomny |
E849419
|
entity |
| Predicate | meetsAtClinic |
P162421
|
FINISHED |
| Object | The Master |
—
|
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: The Master | Statement: [Ivan Bezdomny, meetsAtClinic, The Master]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meetsAtClinic Context triple: [Ivan Bezdomny, meetsAtClinic, The Master]
-
A.
examinedIn
Indicates that one entity is analyzed, inspected, or studied within the context, scope, or setting provided by another entity.
-
B.
encountersDoctor
chosen
Indicates that one entity comes into contact with or meets a doctor in some context or situation.
-
C.
typicalAppointmentContext
Indicates the usual situational setting or circumstances in which an appointment typically occurs.
-
D.
typicalAppointment
Indicates that an appointment represents a standard, usual, or commonly occurring scheduling arrangement between entities.
-
E.
openByAppointment
Indicates that access or availability is provided only at scheduled times arranged in advance, rather than during regular open hours.
- 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_69f3495e0f108190a6a7006f79f9c2c3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:29 a.m.