Triple
T10866668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Business Link |
E256547
|
entity |
| Predicate | hadURL |
P96147
|
FINISHED |
| Object | http://www.businesslink.gov.uk |
—
|
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: http://www.businesslink.gov.uk | Statement: [Business Link, hadURL, http://www.businesslink.gov.uk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadURL Context triple: [Business Link, hadURL, http://www.businesslink.gov.uk]
-
A.
hadBase
Indicates that an entity maintained or operated from a particular base location or primary site.
-
B.
hadFort
Indicates that an entity possessed, controlled, or contained a fort at some time.
-
C.
has
Indicates that one entity possesses, owns, contains, or includes another entity as part of its state or composition.
-
D.
hadRoute
Indicates that an entity (such as a service, vehicle, or system) followed, operated on, or was associated with a specific route.
-
E.
hadRight
Indicates that an entity possessed a legal or moral entitlement to perform an action, access something, or claim something in relation to another entity or situation.
- 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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7516e15448190aefdba1aa635baea |
completed | April 9, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69d70d308dfc81908792f98cfb871392 |
completed | April 9, 2026, 2:21 a.m. |
| PDg | Predicate description generation | batch_69d7101c96708190808fef73199e8482 |
completed | April 9, 2026, 2:34 a.m. |
Created at: April 8, 2026, 9:20 p.m.