Triple
T28923984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dr. Edward Armstrong |
E733593
|
entity |
| Predicate | invitationPretext |
P166255
|
FINISHED |
| Object | medical consultation |
—
|
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: medical consultation | Statement: [Dr. Edward Armstrong, invitationPretext, medical consultation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: invitationPretext Context triple: [Dr. Edward Armstrong, invitationPretext, medical consultation]
-
A.
invitationPurpose
Indicates that an invitation is extended with a specific intended purpose or reason, linking the invitation to what it is meant to achieve or be used for.
-
B.
invitationAuthority
Indicates that one entity has the authority or permission to invite another entity (or others) to participate in an event, group, or activity.
-
C.
mayReceiveInvitationTo
Indicates that one entity is allowed or eligible to be sent an invitation by another entity.
-
D.
isInvited
Indicates that one entity has extended an invitation to another entity to participate in or attend something.
-
E.
invitesParticipationOf
Indicates that one entity actively requests or encourages another entity to take part in an activity, event, or process.
- 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_69f05b0a5cc0819094828367ae204b70 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f66003a3f48190a2ba6da5aafbb5cb |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 28, 2026, 8:22 a.m.