Triple
T6664558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Transport Police Committee |
E151565
|
entity |
| Predicate | hadPrimaryFunction |
P88
|
FINISHED |
| Object | oversight of British Transport Police |
—
|
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: oversight of British Transport Police | Statement: [British Transport Police Committee, hadPrimaryFunction, oversight of British Transport Police]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadPrimaryFunction Context triple: [British Transport Police Committee, hadPrimaryFunction, oversight of British Transport Police]
-
A.
hasPrimaryFunction
chosen
Indicates that one entity serves as the main or principal function or role of another entity.
-
B.
hasPrimaryDuty
Indicates that one entity holds the main or most important responsibility or obligation toward another entity or within a specified context.
-
C.
hadFunction
Indicates that an entity previously served or fulfilled a particular role, purpose, or function.
-
D.
primaryHubFunction
Indicates that an entity serves as the main central node or core facility through which key activities, connections, or operations are coordinated or routed.
-
E.
hasPrimarySee
Indicates that one entity is designated as the main or preferred "see" reference or cross-reference for 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_69c687f5fac48190a09e4838d9c6b45d |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ce738fe88190a5557900efeec7ec |
completed | March 27, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69c6ad09974c81908784300ae218961f |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:02 p.m.