Triple
T30382103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daresbury Laboratory |
E772859
|
entity |
| Predicate | locatedInSciencePark |
P89271
|
FINISHED |
| Object | Sci-Tech Daresbury |
—
|
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: Sci-Tech Daresbury | Statement: [Daresbury Laboratory, locatedInSciencePark, Sci-Tech Daresbury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInSciencePark Context triple: [Daresbury Laboratory, locatedInSciencePark, Sci-Tech Daresbury]
-
A.
hasSciencePark
Indicates that one entity possesses, hosts, or includes a science park associated with it.
-
B.
locatedInScienceCity
Indicates that one entity is situated within or belongs to the geographic or administrative area designated as a science city.
-
C.
locatedInParkVicinity
Indicates that an entity is situated in the area immediately surrounding or near a park.
-
D.
inPark
chosen
Indicates that one entity is located within or inside the boundaries of a park.
-
E.
locatedInParkLikeSetting
Indicates that something is situated within or directly surrounded by an environment resembling a park, typically featuring natural or landscaped outdoor elements.
- 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_69f2248e3444819081b05712dc6873de |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a00b6199c348190b1e90375f737d026 |
completed | May 10, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_6a00b5169a7881909a07167c4188731f |
completed | May 10, 2026, 4:40 p.m. |
Created at: April 29, 2026, 8 p.m.