Triple
T31999288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antrìm |
E817078
|
entity |
| Predicate | hasAssociatedCounty |
P13451
|
FINISHED |
| Object | County Antrim |
—
|
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: County Antrim | Statement: [Antrìm, hasAssociatedCounty, County Antrim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedCounty Context triple: [Antrìm, hasAssociatedCounty, County Antrim]
-
A.
associatedWithCounty
chosen
Indicates that an entity has a relationship or linkage to a specific county, such as jurisdiction, location, or administrative association.
-
B.
hasParentCounty
Indicates that a given county is administratively or geographically contained within, and subordinate to, a specified parent county.
-
C.
associatedWithCountySeat
Indicates that an entity has a relationship or connection to a county’s administrative center or county seat.
-
D.
hasCountyCode
Indicates that an entity is associated with a specific county identified by a standardized county code.
-
E.
hasNearbyCounty
Indicates that one county is geographically close to or directly adjacent to another county.
- 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_69f348f8ce388190ae84376b1f348f12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 1, 2026, 12:14 a.m.