Triple
T34326394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malmesbury campus |
E880874
|
entity |
| Predicate | roleForCompany |
P43130
|
FINISHED |
| Object | main UK research and development hub |
—
|
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: main UK research and development hub | Statement: [Malmesbury campus, roleForCompany, main UK research and development hub]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleForCompany Context triple: [Malmesbury campus, roleForCompany, main UK research and development hub]
-
A.
underlyingCompanyRole
chosen
Indicates the specific function, position, or responsibility an entity holds within or in relation to a company.
-
B.
roleInCompanyLifecycle
Indicates the specific function or responsibility an entity has at a particular stage of a company's lifecycle.
-
C.
belongsToCompany
Indicates that an entity is owned, employed, or otherwise formally associated with a specific company.
-
D.
roleOnPern
Indicates the specific function, position, or duty an entity holds within the context of Pern.
-
E.
roleOfGroup
Indicates the function, responsibility, or position that a group holds within a broader context or structure.
- 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_69f349b9cd508190a996a616903b3e6d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f717836f0c8190b4a397bbac37dd09 |
completed | May 3, 2026, 9:38 a.m. |
| PD | Predicate disambiguation | batch_69f7127a2ff08190b77d00963c9df621 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:58 a.m.