Triple
T31620394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patient Transport Service |
E806879
|
entity |
| Predicate | canBeScheduledBy |
P162028
|
FINISHED |
| Object | Healthcare providers |
—
|
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: Healthcare providers | Statement: [Patient Transport Service, canBeScheduledBy, Healthcare providers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeScheduledBy Context triple: [Patient Transport Service, canBeScheduledBy, Healthcare providers]
-
A.
canSchedule
Indicates that one entity has the ability or permission to arrange or set a time for an event, task, or activity involving another entity.
-
B.
isOnScheduleOf
Indicates that something is included in and follows the planned timing or sequence defined by a particular schedule.
-
C.
isScheduled
Indicates that an event, task, or action has been planned and assigned a specific time or time range to occur.
-
D.
scheduledBy
chosen
Indicates that an event, task, or appointment has been arranged or planned by a particular agent or entity.
-
E.
canBeAssignedTo
Indicates that one entity is eligible or permitted to be allocated, designated, or linked to another entity for a particular purpose or role.
- 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_69f348d7883c8190b6c13ab92b7ef076 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd91a5dad8819093eeeef527027890 |
completed | May 8, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69fd8f65fe9081908902500a3228d935 |
completed | May 8, 2026, 7:23 a.m. |
Created at: April 30, 2026, 10:40 p.m.