Triple
T2664439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yellow Card Scheme |
E55600
|
entity |
| Predicate | reportsCanBeSubmittedBy |
P2810
|
FINISHED |
| Object | healthcare professionals |
—
|
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 professionals | Statement: [Yellow Card Scheme, reportsCanBeSubmittedBy, healthcare professionals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reportsCanBeSubmittedBy Context triple: [Yellow Card Scheme, reportsCanBeSubmittedBy, healthcare professionals]
-
A.
reportsThrough
Indicates that one entity formally communicates and is accountable to another entity through an established reporting or supervisory chain.
-
B.
reportsWithin
Indicates that one entity submits or delivers a report to another entity within a specified time frame or boundary.
-
C.
canReport
chosen
Indicates that one entity has the ability or permission to report on, or submit a report about, another entity or situation.
-
D.
reportsImplementedBy
Indicates that a report is realized, produced, or carried out by a specific implementing entity or system.
-
E.
requiresReportTo
Indicates that one entity is obligated to submit or provide a report to 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_69ab49e54de48190be708cd1cf8be073 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd96dba44819085c3e651afba7806 |
completed | March 7, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69abd81768748190bd965f367cf6ef37 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:54 p.m.