Triple
T13649945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Talgje parish |
E326704
|
entity |
| Predicate | servedCommunityType |
P25084
|
FINISHED |
| Object | rural island communities |
—
|
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: rural island communities | Statement: [Talgje parish, servedCommunityType, rural island communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedCommunityType Context triple: [Talgje parish, servedCommunityType, rural island communities]
-
A.
servesCommunitiesAlong
Indicates that something provides services or support to the communities located along a particular route, corridor, or area.
-
B.
organizationTypeServed
Indicates the type of organization that is served or supported by a given entity or activity.
-
C.
hasCommunityServed
chosen
Indicates that an entity provides services or benefits to, or is intended to support, a particular community or group of people.
-
D.
cityServedType
Indicates the type or category of city that is served by a given entity (such as a facility, service, or infrastructure).
-
E.
townServed
Indicates that a given service, facility, or infrastructure serves or provides coverage to a particular town.
- 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_69d8076d8270819092afc2f0e9c359a8 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc608466c81908f6d2c9c92cc86aa |
completed | April 12, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8a027081908d8f884b89707a5e |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:52 p.m.