Triple
T3377692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Other |
E71105
|
entity |
| Predicate | connectionToDoctor |
P37306
|
FINISHED |
| Object | essence linked to the Doctor’s origins |
—
|
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: essence linked to the Doctor’s origins | Statement: [the Other, connectionToDoctor, essence linked to the Doctor’s origins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectionToDoctor Context triple: [the Other, connectionToDoctor, essence linked to the Doctor’s origins]
-
A.
connectionTo
chosen
Indicates a relationship in which one entity is linked, associated, or otherwise related to another entity.
-
B.
appointmentType
Indicates the specific category or nature of an appointment associated with an entity or event.
-
C.
consultationMethod
Indicates the way or medium through which a consultation is conducted or delivered.
-
D.
publicConsultationHeld
Indicates that a formal public consultation process has been conducted regarding a particular decision, policy, or project.
-
E.
typicalAppointment
Indicates that an appointment represents a standard, usual, or commonly occurring scheduling arrangement between entities.
- 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_69ad85a7f80c8190a05e43013f298942 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb2e8d1988190b6fb6c4c5502f25f |
completed | March 8, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69ada433059881908e46f38cc5f40a32 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:13 p.m.