Triple
T2605854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Employment Service |
E58655
|
entity |
| Predicate | usedFacilityName |
P41182
|
FINISHED |
| Object | Jobcentre |
—
|
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: Jobcentre | Statement: [Employment Service, usedFacilityName, Jobcentre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedFacilityName Context triple: [Employment Service, usedFacilityName, Jobcentre]
-
A.
isNamedFacilityOf
Indicates that a facility bears the official name associated with a particular entity (such as an organization, person, or place).
-
B.
userFacility
Indicates a relationship where a user is associated with, has access to, or operates within a particular facility.
-
C.
servesFacility
Indicates that one entity provides services or support to a particular facility as its client, target, or area of operation.
-
D.
legacyFacilityOf
Indicates that one facility is an older, predecessor, or superseded version of another facility within the same organizational or operational context.
-
E.
nameUsedToAccommodate
Indicates that a particular name was previously used to refer to or accommodate an entity, but is no longer its current or primary name.
- F. None of above. chosen
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_69ab4ac3523881909679750c9f8c2dec |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd8def9bc8190b2e013abffc7b191 |
completed | March 7, 2026, 7:50 a.m. |
| PD | Predicate disambiguation | batch_69abd80ab7248190ba06ba14fe4c5638 |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd8dd05c48190b4f90031642c4091 |
completed | March 7, 2026, 7:50 a.m. |
Created at: March 6, 2026, 9:49 p.m.