Triple
T35299530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bombe |
E1019465
|
entity |
| Predicate | modernReconstructionLocation |
P18377
|
FINISHED |
| Object | Bletchley Park museum |
—
|
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: Bletchley Park museum | Statement: [Bombe, modernReconstructionLocation, Bletchley Park museum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernReconstructionLocation Context triple: [Bombe, modernReconstructionLocation, Bletchley Park museum]
-
A.
modernizationLocation
Indicates the place or setting where a modernization process or upgrade occurs.
-
B.
majorRestorationLocation
chosen
Indicates the primary place where a significant restoration or refurbishment of an object, structure, or work was carried out.
-
C.
historicalReconstruction
Indicates the process of recreating or inferring past events, conditions, or states of affairs based on available evidence or records.
-
D.
reconstructionOrRestorationDate
Indicates the date on which an entity was reconstructed or restored after damage, alteration, or deterioration.
-
E.
modernLocality
Indicates that an entity is located in, associated with, or corresponds to a present-day geographic or administrative locality.
- 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_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
Created at: May 3, 2026, 4:03 p.m.