Triple
T2064579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Hospital for Children and Young People |
E45867
|
entity |
| Predicate | hasPatientGroup |
P35131
|
FINISHED |
| Object | children with complex needs |
—
|
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: children with complex needs | Statement: [Royal Hospital for Children and Young People, hasPatientGroup, children with complex needs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPatientGroup Context triple: [Royal Hospital for Children and Young People, hasPatientGroup, children with complex needs]
-
A.
hasPatient
Indicates that an action, event, or process involves a specific entity as the one undergoing or receiving its effects (the patient).
-
B.
hasUserGroup
Indicates that a user is associated with, belongs to, or is a member of a specific user group.
-
C.
hasStationGroup
Indicates that an entity is associated with, or belongs to, a particular group or collection of stations.
-
D.
hasCentralGroup
Indicates that an entity possesses or is associated with a primary or central group within its structure or organization.
-
E.
hasMembers
Indicates that a group, organization, or collection includes certain entities as its members.
- 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_69a8891b38288190abd572ccad9b6928 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9d5147c8190a264fe42f0634cec |
completed | March 7, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69abb7aee9b48190999620176e3a6ee2 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb87b9fc08190a748c278ef2d7dc7 |
completed | March 7, 2026, 5:32 a.m. |
Created at: March 4, 2026, 7:40 p.m.