Triple
T38604973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serco-Abellio joint venture |
E934316
|
entity |
| Predicate | componentCompany |
P13459
|
FINISHED |
| Object | Serco Group plc |
—
|
NE NERFINISHED |
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: Serco Group plc | Statement: [Serco-Abellio joint venture, componentCompany, Serco Group plc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: componentCompany Context triple: [Serco-Abellio joint venture, componentCompany, Serco Group plc]
-
A.
memberCompany
chosen
Indicates that a company is formally part of, or affiliated as a member with, a larger organization, group, or association.
-
B.
featuresCompany
Indicates that one entity prominently presents, highlights, or showcases a company, typically as part of content, listings, or promotional material.
-
C.
company
Indicates that an entity is a business organization engaged in commercial, industrial, or professional activities.
-
D.
hasCompanyName
Indicates that an entity is associated with or identified by a specific company name.
-
E.
publicCompany
Indicates that a company is publicly traded, meaning its ownership shares are available to the general public on one or more stock exchanges.
- 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_69f76ecc17688190b389b693a5927501 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe38be079c8190a240191ac0e73e3a |
completed | May 8, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69fe350344508190930de2218156ca02 |
completed | May 8, 2026, 7:09 p.m. |
Created at: May 3, 2026, 4:32 p.m.