Triple
T32305396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lister district |
E825349
|
entity |
| Predicate | regionalCenterTown |
P117896
|
FINISHED |
| Object | Flekkefjord |
—
|
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: Flekkefjord | Statement: [Lister district, regionalCenterTown, Flekkefjord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionalCenterTown Context triple: [Lister district, regionalCenterTown, Flekkefjord]
-
A.
isTownCenterOf
Indicates that a location functions as the central, primary area or hub of a specified town.
-
B.
servesAsRegionalCenterFor
chosen
Indicates that one entity functions as the primary administrative, economic, or service hub for a surrounding region or group of entities.
-
C.
majorTownInRegion
Indicates that a town is one of the principal or most significant towns within a specified region.
-
D.
hasCentralTownFeature
Indicates that a town possesses a specific central feature or focal element (such as a landmark, square, or facility) that characterizes its core area.
-
E.
hasRegionalCentresIn
Indicates that an entity maintains one or more regional centers located in the specified place or area.
- 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_69f349115304819084ee91d345b6c8aa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fed48d8e148190a99c0aea29f8a3ee |
completed | May 9, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fed3c82a24819095e614e31ac0307f |
completed | May 9, 2026, 6:27 a.m. |
Created at: May 1, 2026, 12:45 a.m.