Triple
T38521200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glyndyfrdwy |
E922476
|
entity |
| Predicate | hasModernPrincipalArea |
P43602
|
FINISHED |
| Object | Denbighshire |
—
|
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: Denbighshire | Statement: [Glyndyfrdwy, hasModernPrincipalArea, Denbighshire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModernPrincipalArea Context triple: [Glyndyfrdwy, hasModernPrincipalArea, Denbighshire]
-
A.
hasModernLocation
chosen
Indicates that an entity is currently situated in, or corresponds to, a specified modern geographic or administrative location.
-
B.
hasModernLocationStatus
Indicates that an entity’s current or contemporary geographic location status is being specified or characterized.
-
C.
hasModernSection
Indicates that an entity includes or contains a distinct section devoted to modern or contemporary content, features, or aspects.
-
D.
hasModernAccessPoint
Indicates that one entity provides or includes a contemporary means or facility through which another entity can be accessed or used.
-
E.
hasModernSquare
Indicates that an entity possesses or includes a square-shaped feature designed or styled in a modern way.
- 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_69f76ea5f5588190bd0b28c82e975640 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffcb5536d88190bfc2e00b854cacfb |
completed | May 10, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69ffc900c2a081909dea04aa60566923 |
completed | May 9, 2026, 11:53 p.m. |
Created at: May 3, 2026, 4:32 p.m.