Triple
T31558680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Mary’s Church, Brecon |
E805197
|
entity |
| Predicate | locatedInMarketTown |
P104671
|
FINISHED |
| Object | Brecon |
E230273
|
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: Brecon | Statement: [St Mary’s Church, Brecon, locatedInMarketTown, Brecon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInMarketTown Context triple: [St Mary’s Church, Brecon, locatedInMarketTown, Brecon]
-
A.
isInMarketTown
chosen
Indicates that an entity is located within or belongs to a town that functions as a local commercial or trading center.
-
B.
containsMarketTown
Indicates that one region or area includes within its boundaries a town that functions as a market center.
-
C.
situatedInTown
Indicates that one entity is located within the geographical or administrative boundaries of a specific town.
-
D.
marketTown
Indicates that a town functions as a local commercial center where markets are regularly held for trade and exchange.
-
E.
locatedInPlannedTown
Indicates that an entity is situated within the boundaries of a town that has been deliberately planned or designed rather than having developed organically.
- 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_69f348d22e088190ad555d5bd42f9da0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a01ac8b4ac881908aa52079c985ddac |
completed | May 11, 2026, 10:16 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b5643ea4c8190b10539fc926c4200 |
completed | June 12, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_6a01aa7fa7b48190b4911aa6bcabe7eb |
completed | May 11, 2026, 10:07 a.m. |
Created at: April 30, 2026, 10:14 p.m.