Triple
T24480661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lough Gur |
E617360
|
entity |
| Predicate | hasStoneCircle |
P115854
|
FINISHED |
| Object | Grange stone circle |
—
|
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: Grange stone circle | Statement: [Lough Gur, hasStoneCircle, Grange stone circle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStoneCircle Context triple: [Lough Gur, hasStoneCircle, Grange stone circle]
-
A.
numberOfStoneCircles
Indicates the quantity of stone circles associated with or present in a given entity or context.
-
B.
hasStoneMonument
chosen
Indicates that one entity possesses, contains, or features a stone monument associated with it.
-
C.
hasArchaeologicalMound
Indicates that an entity possesses or contains an archaeological mound, i.e., a raised earthwork or mound of archaeological significance located on or within it.
-
D.
hasArchaeologicalSiteIn
Indicates that an entity possesses, contains, or is associated with an archaeological site located within a specified place or region.
-
E.
hasNearbyArchaeologicalSite
Indicates that an entity is located close to or in the vicinity of an archaeological site.
- 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_69e2d7f3ae788190b683394db15f220e |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29ed5d4388190a8a6ce4079aa8a54 |
completed | April 30, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:21 a.m.