Triple
T4635246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newry |
E101512
|
entity |
| Predicate | foundedAsReligiousSite |
P24856
|
FINISHED |
| Object | by Saint Patrick (tradition) |
—
|
LITERAL 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: by Saint Patrick (tradition) | Statement: [Newry, foundedAsReligiousSite, by Saint Patrick (tradition)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsReligiousSite Context triple: [Newry, foundedAsReligiousSite, by Saint Patrick (tradition)]
-
A.
foundedOnSiteOf
Indicates that something was established or built at the same physical location where another, earlier entity or structure previously existed.
-
B.
foundedReligion
Indicates that an entity established or originated a particular religion.
-
C.
hasReligiousSite
Indicates that a location or entity possesses, contains, or is associated with a religious site such as a temple, church, mosque, shrine, or similar place of worship.
-
D.
foundedAsShrine
chosen
Indicates that an entity was originally established or created as a shrine.
-
E.
foundedCityOnSiteOf
Indicates that a city was established on the same physical location where another settlement or city previously existed.
- 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_69bd43d2f1c081908cd4b7ec48ecc73d |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a60a66c8190b76f3d3a7da1df55 |
completed | March 20, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69bd5233cb5081908807e2b150f0ca06 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:13 p.m.