Triple
T35299545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Block D (Bletchley Park) |
E1019466
|
entity |
| Predicate | replacedWorkPreviouslyDoneIn |
P196103
|
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), replacedWorkPreviouslyDoneIn, wooden huts at Bletchley Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedWorkPreviouslyDoneIn Context triple: [Block D (Bletchley Park), replacedWorkPreviouslyDoneIn, wooden huts at Bletchley Park]
-
A.
replacedInSomeWorkflowsBy
Indicates that in certain workflows or processes, one entity is substituted or superseded by another.
-
B.
replacedDuring
Indicates that one entity took the place of another entity during a specified time period or interval.
-
C.
materialWorked
Indicates that an agent performs work or processing on a specified material.
-
D.
previousWorkAfterHiatusOf
Indicates that one work directly follows and resumes activity after a hiatus or break from a previous work.
-
E.
repairsCompleted
Indicates that a previously initiated repair action or process has been fully carried out and successfully finished.
- 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_69f76de7eedc8190a3bdc64ebbc05b42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe066d62b48190867df334039be786 |
completed | May 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69fe03afde3c8190a5b9b0778d19eb1a |
completed | May 8, 2026, 3:39 p.m. |
| PDg | Predicate description generation | batch_69fe066b623c819085205fbea901e3cf |
completed | May 8, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:03 p.m.