Triple
T31612941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mold, Flintshire |
E806673
|
entity |
| Predicate | nearbyFindHousedAt |
P194257
|
FINISHED |
| Object | British 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: British Museum | Statement: [Mold, Flintshire, nearbyFindHousedAt, British Museum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyFindHousedAt Context triple: [Mold, Flintshire, nearbyFindHousedAt, British Museum]
-
A.
residesNear
Indicates that one entity lives or is located in close physical proximity to another entity.
-
B.
houseLocatedIn
Indicates that a house is situated within or belongs to a specific geographic location or area.
-
C.
inResidenceAt
Indicates that an entity lives or resides at a particular location or residence.
-
D.
hasNearbyLodge
Indicates that one entity is located close to or in the vicinity of a lodge associated with another entity.
-
E.
hasNearbyPropertyType
Indicates that one entity has another entity of a specified property type located in close physical proximity to it.
- 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_69f348d61f2081908cad94bc9ffbb671 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
| PDg | Predicate description generation | batch_69fd68ab21a0819096bfc4a8c14851ad |
completed | May 8, 2026, 4:38 a.m. |
Created at: April 30, 2026, 10:37 p.m.