Triple
T34378778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linköping region |
E882367
|
entity |
| Predicate | hasStrongLocalIdentity |
P59181
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Linköping region, hasStrongLocalIdentity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStrongLocalIdentity Context triple: [Linköping region, hasStrongLocalIdentity, true]
-
A.
hasIdentity
Indicates that one entity is the same as, or is identified as, another specific entity or identifier.
-
B.
hasGlobalIdentity
Indicates that an entity possesses a unique, overarching identity that is recognized or valid across multiple systems, contexts, or domains.
-
C.
localIdentity
chosen
Indicates that an entity’s identity or role is defined specifically within a particular local context, scope, or environment, rather than globally.
-
D.
hasIdentityComponent
Indicates that an entity includes or is associated with a specific component that contributes to or defines its identity.
-
E.
hasNeighborhoodIdentity
Indicates that an entity possesses or is associated with a distinctive neighborhood-based character, culture, or identity.
- 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_69f349bf5d7481908dd5da4cbdf74047 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff90b673248190b4dda9e005642d17 |
completed | May 9, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69ff8d5bee1081909274052945e98a6f |
completed | May 9, 2026, 7:39 p.m. |
Created at: May 1, 2026, 1:59 a.m.