Triple
T28138704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BRS Contract Hire |
E714281
|
entity |
| Predicate | originatedAsPartOf |
P2612
|
FINISHED |
| Object | British Road Services |
—
|
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: British Road Services | Statement: [BRS Contract Hire, originatedAsPartOf, British Road Services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originatedAsPartOf Context triple: [BRS Contract Hire, originatedAsPartOf, British Road Services]
-
A.
originatesAs
Indicates that one entity begins, arises, or comes into existence in the form, state, or role specified by another entity.
-
B.
foundedAsPartOf
chosen
Indicates that an entity was established as a component, division, or subset of a larger existing organization, project, or structure.
-
C.
usedToBePartOf
Indicates that an entity was formerly a component or member of another entity but is no longer part of it.
-
D.
raisedAsPartOf
Indicates that an entity was brought up, nurtured, or developed within the context, environment, or membership of another entity or group.
-
E.
builtAsPartOf
Indicates that one entity was constructed as a component or subset of a larger, encompassing entity or project.
- 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_69efd6af156c81908f50c2cd7db0e1ef |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69fe7b1c506c8190869c1a22031e0571 |
completed | May 9, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69fe796b2bdc8190a86980d44008f875 |
completed | May 9, 2026, 12:01 a.m. |
Created at: April 27, 2026, 9:51 p.m.