Triple
T36011782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lynk & Co |
E1041730
|
entity |
| Predicate | designCenterLocation |
P99684
|
FINISHED |
| Object | Gothenburg |
—
|
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: Gothenburg | Statement: [Lynk & Co, designCenterLocation, Gothenburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designCenterLocation Context triple: [Lynk & Co, designCenterLocation, Gothenburg]
-
A.
designCenter
chosen
Indicates that an entity serves as the primary location or hub where another entity is designed or conceptually developed.
-
B.
designLocation
Indicates the place or setting where something is conceived, planned, or designed.
-
C.
designPositioning
Indicates the spatial or conceptual placement of a design element relative to other elements or a defined reference.
-
D.
engineeringLocation
Indicates the place where engineering-related work, design, or technical development for an entity is carried out.
-
E.
platformLocation
Indicates the spatial position or placement of a platform relative to a reference point or environment.
- 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_69f76e2b981881908e4e160607fa82eb |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff289541e0819096eeceb8e6332650 |
completed | May 9, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69ff281ab1988190920f0443be9f10cc |
completed | May 9, 2026, 12:27 p.m. |
Created at: May 3, 2026, 4:07 p.m.