Triple
T33595278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ballysillan |
E860544
|
entity |
| Predicate | locatedInHistoricTerritory |
P80777
|
FINISHED |
| Object | County Antrim |
E44037
|
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: County Antrim | Statement: [Ballysillan, locatedInHistoricTerritory, County Antrim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInHistoricTerritory Context triple: [Ballysillan, locatedInHistoricTerritory, County Antrim]
-
A.
locatedInHistoricSite
Indicates that an entity is situated within or on the grounds of a place officially recognized as a historic site.
-
B.
partOfHistoricalArea
Indicates that one entity is located within or belongs to a designated historical area or heritage zone.
-
C.
historicallyLocatedOutside
Indicates that an entity was historically situated beyond the boundaries or limits of another specified place or region.
-
D.
historicallyPartOf
Indicates that one entity was formerly a component, region, or subdivision of another entity during a past historical period, but is not necessarily part of it in the present.
-
E.
locatedInProvinceHistorical
chosen
Indicates that an entity was situated within a specific province during a historical period or according to historical administrative boundaries.
- 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_69f3497f35908190a2e9bbb9b96c7a3f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a365c53000481908785a857a852bf43 |
completed | June 20, 2026, 9:24 a.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:41 a.m.