Triple
T31409132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turks in Switzerland |
E801211
|
entity |
| Predicate | integrationIssue |
P177360
|
FINISHED |
| Object | language integration |
—
|
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: language integration | Statement: [Turks in Switzerland, integrationIssue, language integration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: integrationIssue Context triple: [Turks in Switzerland, integrationIssue, language integration]
-
A.
deploymentIssue
Indicates that there is a problem, error, or obstacle affecting the deployment of a system, application, or component.
-
B.
integrationOutcome
Indicates the result or consequence produced when two or more components, systems, or processes are combined or integrated.
-
C.
integrationFeature
Indicates that one entity provides a capability or component specifically intended to enable or support integration with another system, service, or component.
-
D.
integrates
Indicates that one entity combines or brings together another entity or set of entities into a unified, functioning whole.
-
E.
integrationGoal
Indicates that one entity has the objective or intended outcome of being combined, unified, or made interoperable with another entity or system.
- F. None of above. chosen
Provenance (4 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_69f348c0dd648190bf2fd7642f78eb06 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6fb93224881908fc66fe76115fcdb |
completed | May 3, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f6fb17d5ec81909091e37e1ddbe577 |
completed | May 3, 2026, 7:36 a.m. |
Created at: April 30, 2026, 8:36 p.m.