Triple
T36912861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lokeren region |
E912959
|
entity |
| Predicate | regionalIdentityLinkedTo |
P117178
|
FINISHED |
| Object | K.S.C. Lokeren Oost-Vlaanderen |
—
|
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: K.S.C. Lokeren Oost-Vlaanderen | Statement: [Lokeren region, regionalIdentityLinkedTo, K.S.C. Lokeren Oost-Vlaanderen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionalIdentityLinkedTo Context triple: [Lokeren region, regionalIdentityLinkedTo, K.S.C. Lokeren Oost-Vlaanderen]
-
A.
hasRegionalIdentity
Indicates that an entity possesses or is associated with a specific regional or local identity.
-
B.
shareRegionalIdentityWith
chosen
Indicates that two entities are perceived to belong to or identify with the same geographic, cultural, or regional community.
-
C.
hasRegionalEntity
Indicates that one entity includes, governs, or is associated with another entity that functions as its regional subdivision or component.
-
D.
linkedToRegion
Indicates that one entity is associated or connected to a specific geographic or administrative region.
-
E.
regionOfAssociation
Indicates a broader geographic or spatial area with which an entity is functionally, contextually, or organizationally associated.
- 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_69f76e879768819085c2fb31a6a5b44b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a003f6083608190a5deadc7291cf70e |
completed | May 10, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_6a003c935c40819085fdb255a52ba03b |
completed | May 10, 2026, 8:06 a.m. |
Created at: May 3, 2026, 4:13 p.m.