Triple
T37559581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ormond, Ireland |
E933779
|
entity |
| Predicate | notableTownWithinHistoricalArea |
P14082
|
FINISHED |
| Object | Kilkenny |
E250779
|
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: Kilkenny | Statement: [Ormond, Ireland, notableTownWithinHistoricalArea, Kilkenny]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTownWithinHistoricalArea Context triple: [Ormond, Ireland, notableTownWithinHistoricalArea, Kilkenny]
-
A.
containsHistoricTown
Indicates that one entity geographically includes or encompasses a town that has recognized historical significance.
-
B.
historicalMainTown
Indicates that one place served as the primary or principal town for another place during a specific historical period.
-
C.
hasNotableTown
chosen
Indicates that an entity includes or is associated with a town that is considered notable or significant in some way.
-
D.
notableRegionOfSettlement
Indicates that a specified region is a significant or prominent place where an entity is or has been settled.
-
E.
historicalTownName
Indicates that the object is a former or historical name by which the town (subject) was previously known.
- 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_69f76ecb4acc8190b53f96d0b013e415 |
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_6a40fb6692748190adc692f7f4cc7106 |
completed | June 28, 2026, 10:45 a.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.