Triple
T35299546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Block D (Bletchley Park) |
E1019466
|
entity |
| Predicate | expandedWorkPreviouslyDoneIn |
P44667
|
FINISHED |
| Object | wooden huts at Bletchley Park |
—
|
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: wooden huts at Bletchley Park | Statement: [Block D (Bletchley Park), expandedWorkPreviouslyDoneIn, wooden huts at Bletchley Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expandedWorkPreviouslyDoneIn Context triple: [Block D (Bletchley Park), expandedWorkPreviouslyDoneIn, wooden huts at Bletchley Park]
-
A.
relatedWorkBefore
Indicates that one work is temporally or sequentially related to another work that precedes it.
-
B.
includedWorkOn
chosen
Indicates that one entity contains, features, or incorporates another entity as a work or component within it.
-
C.
previousWorkAfterHiatusOf
Indicates that one work directly follows and resumes activity after a hiatus or break from a previous work.
-
D.
hasWorkedIn
Indicates that a person has been employed or has performed work within a particular organization, location, or domain for some period of time.
-
E.
expandsOnWork
Indicates that one work builds upon, elaborates, or extends the content, ideas, or results of another work.
- 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_69f76de7eedc8190a3bdc64ebbc05b42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:03 p.m.