Triple
T35313312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Welchman |
E1019836
|
entity |
| Predicate | notablePlaceAssociation |
P78460
|
FINISHED |
| Object | Bletchley Park |
E78812
|
NE 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: Bletchley Park | Statement: [Welchman, notablePlaceAssociation, Bletchley Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePlaceAssociation Context triple: [Welchman, notablePlaceAssociation, Bletchley Park]
-
A.
notableSiteAssociatedWith
chosen
Indicates that there is a significant or noteworthy site or location that is associated with, related to, or prominently linked to the given entity.
-
B.
notableBuildingAssociated
Indicates a relationship where a notable or significant building is associated with, connected to, or relevant to a given entity.
-
C.
notablePlace
Indicates that a place is especially significant, famous, or noteworthy in relation to the subject.
-
D.
hasFamousAssociationWith
Indicates a notable or widely recognized connection or relationship between two entities, often due to public attention, historical significance, or cultural impact.
-
E.
notableLocation
Indicates that a location is especially significant, prominent, or noteworthy in relation to the subject.
- F. None of above.
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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3819e7ce3c8190a3e68b725ce52848 |
completed | June 21, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.