Triple
T24631615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal College of Paediatrics and Child Health |
E609689
|
entity |
| Predicate | hasSubsidiaryUnit |
P11471
|
FINISHED |
| Object | RCPCH Global |
E609689
|
NE 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: RCPCH Global | Statement: [Royal College of Paediatrics and Child Health, hasSubsidiaryUnit, RCPCH Global]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubsidiaryUnit Context triple: [Royal College of Paediatrics and Child Health, hasSubsidiaryUnit, RCPCH Global]
-
A.
hasSubsidiaryBusiness
Indicates that one business entity owns or controls another business entity as its subsidiary.
-
B.
subsidiaryUnit
chosen
Indicates that one organizational unit functions as a subordinate or dependent division of another, higher-level unit.
-
C.
hasSubsidiaryLabel
Indicates that one entity is identified as a subsidiary or subordinate organization of another entity.
-
D.
hasSubsidiaryTop
Indicates that one organization is the primary or top-level parent of another organization that operates as its subsidiary.
-
E.
usedBySubsidiaryOf
Indicates that something is used by an entity that is a subsidiary of another organization.
- F. None of above.
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_69e2c4d1d3708190a0f2dc6a3a8523bb |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be064ff88190b5d9e5ec75a41242 |
completed | April 30, 2026, 2:27 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a100fef08a88190b88f5f3e67ff273c |
completed | May 22, 2026, 8:12 a.m. |
| PD | Predicate disambiguation | batch_69f2a6d0ab708190b2e3b94dd20ca76b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:32 a.m.