Triple
T37654081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wells (UK Parliament constituency) |
E937248
|
entity |
| Predicate | notableLandmarkInSeat |
P153329
|
FINISHED |
| Object | Wells Cathedral |
E138146
|
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: Wells Cathedral | Statement: [Wells (UK Parliament constituency), notableLandmarkInSeat, Wells Cathedral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableLandmarkInSeat Context triple: [Wells (UK Parliament constituency), notableLandmarkInSeat, Wells Cathedral]
-
A.
notableLocationOn
Indicates that a particular location is especially significant or noteworthy in relation to a specified entity or context.
-
B.
notablePlace
Indicates that a place is especially significant, famous, or noteworthy in relation to the subject.
-
C.
containsNotablePlace
chosen
Indicates that one location includes within its boundaries a place that is considered notable or significant.
-
D.
cityLandmarkID
Indicates that a specific landmark is uniquely identified as being located within a particular city.
-
E.
seatOfMetropolitan
Indicates that one entity serves as the central administrative or ecclesiastical seat of a metropolitan authority or jurisdiction for another entity.
- 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_69f76ed4fe908190b8061c5c135e0971 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40d66a02888190a54b9462f88465e1 |
completed | June 28, 2026, 8:08 a.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.